SiMPLE | Forum

Ok fixed again. Still not sure exactly what did it, but...

- Installed  battlefield_1942_gamespy_patch_v1.61 from  http://team-simple.org/download/
- Installed FHSW_v0.552_Setup_Part_2 from http://www.moddb.com/mods/forgotten-hop … /downloads (you probably need part 1 and FH installed for it to work, but I already had them, see previous posts).
- And at some point I think I updated the AMD drivers again.
- Also continually messed about with compatibility settings. Ultimately they still need setting off (unticked) on both bf1942.exe and blackscreen.exe to work.

Anyway, few restarts later, it's fine. Hopefully. Until the next driver release...

Vietnam. It's one of the longest running 1942 mods - they also did a BF2 mod which I thought was great but dissapeared quite quick.

Previously a decent size team, now coded by one guy - Lotte - and has a stupidly large numer of maps (100s), custom everything, all very polished, imported a load of stuff from BF:V, and is generally a pretty fast-action DC style mod without all the techy tricks (spawns/nukes/etc) that DC did.

EOD:Redux is basically Lotte starting from scratch in the Unreal engine, albeit importing a lot of the maps.

Random fact - the Snoopy logo on the M113 apc is a tribute to an old EOD mod team member who died.

what driver version / os have you got bud?

I've never seen this issue except with the latest drivers (16.1). Before that I was whatever is default in win 10 vanialla (15.00??), before that something old aswell (prob early 15s or 14 something).

So turns out this may all have been an AMD Radeon driver issue after all.

Updated to latest Crimson edition (the only *other* thing installed alongside the 360 drivers) and.... almost the same thing. DINPUT8.dll errors. Plus side is this time it's only doing it when map changes (or when changing between mods). I can load up one map fine. Which is good enough. Though I'm already trying to download the older non-Crimson edition Radeon drivers (before 15.11) - see if that helps.

EDIT: Nope, 15.7 just CTDs all the time, as OP. Going back to 16.1 to see if it at least boots... :\

Win 10 Tip 2: Don't update Radeon drivers. Like, ever.

EDIT 2: 16.1s got back to at least running, crashing during map/mod change. Good enough I guess. Maybe they'll fix it in a later release...

Tip 3: Nvidia.

Stuff I'm finding out:

1. Unless windows  has *vastly* improved over the last few years, Win 10 Reset doesn't entirely remove everything. Unless they're very specific with their choice of default drivers (both proper ATI ones, and Gigabyte branded realtek audio drivers - specific to my mobo - *really*?? ).

2. The DINPUT8.dll error is pretty generic. I'm getting it for tons of reasons (ctd during map changes, etc).

3. It crashes *a lot* on Win 10.

4. The pause during map load at 25% (where it just loads a tiny bit reaaalll slow and keeps doing it forever) *could* be caused by a firewall block. Eg. fresh install, try to load map, stops, then I notice firewall exception prompt, exempt bf1942.exe, then map loads fine.

5. Vanialla is pretty much fine.

6. Mods (FH / FHSW all i have atm) still have exactly same error - on map load (if started via vanialla), or using their desktop shortcuts to run (immidiate DINPUT8.dll error).

7. losing the will to live

Thanks trench, and yeah - it's all pretty much been covered. No DirectX stuff to uninstall.

From what I can tell, the 360 drivers installed a modified directx 9.0c alongside the 12 built in to win 10. And this survives a restore point without any obvious services or software that can be removed (or at least enough of it survives to mess up the current install within 10 odd mins of a restore, give or take a net connection) other than the stuff I've already done - namely uninstalling the Xbox 360 Accessories software. I've uninstalled anything I can through dev manager but actually never had a 360 controller anyway (it was a long shot to get something else working...).

In addition, I can't "update" 9.0c to a correct version as the 9.0c installer refuses due to currently being "up to date". Extracting, and trying to regedit some directx version numbers didn't get it going. And I can't uninstall it because officially I only have DirectX 12 installed, which can't be uninstalled (or is a very bad idea)

FWIW, 1942 does start up in compatibility mode, it just hangs on map load (presumably whilst it's loading control drivers).

Full restore next week then. Failing that, hopefully the win 7 image still works... (with 1942 preinstalled ) Honestly I'm stumped - none of it really makes sense - how the hell does a driver / dx version that no longer exists after a restore, somehow reappear with a net connection despite having been both uninstalled and techincally never having been installed (given the restore point). almost makes me want to packet sniff everything. but i have a life

Thanks nämeless, but I can't find anything obvious.

Win 10 doesn't have the best windows update system - you can't use it online as previously, and the inbuilt system barely shows any details. That said, it's showing no updates at all during the time things went wrong, and nothing since.

Graphics afaik isn't updaing anything. Nothing obvious in task scheduler (DirectX, HID, input, DS4Windows, driver, whatever related). Same with services.

I'm gonna try find out from the DS4Windows dev if they have anything that could be doing anything online, or anything that would survive an uninstall and system restore. Otherwise, full restore it is

Ok so... where's the best techy 1942 forum? This is getting weird.

If I roll back to before the "Install DirectX" system restore point (which was initiated on exactly the same day / time as I was messing aroudn with DS4Windows and general pad / Dinput / Xinput drivers) it's fine, UNTIL I connect to internet, then within a few minutes it's borked again.

I've tried uninstalling any drivers / 360 pad program / ds4windows / whatever I can, but clearly something appears to be updating online and mucking up something control related. could be a windows update for something completely unrelated, but seems a little bit too much of a coincidence not to be ds4windows related.

system32/dinput8.dll file is showing no file access since October, so maybe some dependency file.

Anyone know enough about 1942's dinput useage to have any idea what's happened and how to fix it? Also, system32 folder not allowing me file write access even as admin

and bud - DirectX is inbuilt in windows 10. Only way to "install" or "reinstall" it is to do so for the whole OS. which is probably my next trick, after trying it with 1942 to see if it's just a control config file issue.

Yep I got that

So anyway, tip for 1942 players: don't install DS4Windows (Playstation DualShock drivers) or the official Microsoft Win 7 Xbox 360 control pad drivers.

One, the other, or a combination of the two, update DirectX (ie. DINPUT8.dll as bud says) which for whatever reason then stops 1942 from working as above.

Had to system restore back to a previous state to solve that one. Never thought I'd be thankful for system restore

Double tip: if you need to do exactly this, you need to restore to the restore point *before* the "Installed DirectX" restore point (if you select that exact point, it still won't work). So pray to god you have additional restore points before this. I had 1 left. Lucky, lucky me... .

Hey, it was trapo on the forgottenhonor forums who told me this (see http://forgottenhonor.com/modules.php?n … post651858 ), i don't have any more info but asked him to send you details if it's important.

Also, do you know what this is: http://www.mediafire.com/download/zgvht … creen-fix_
Looks like a team-simple release for CD only but the init.con says 1.61 despite the file title and nfo saying 1.612. And I'm pretty sure I've tried it before and it doesn't work.

EDIT: Oh that actually seems to work http://www.mediafire.com/download/zgvht … creen-fix_ CD version says 1.612 ingame, and just got me conntected to an origin (1.612) only server with true widescreen. Now I'm just missing an origin version of the same thing.

EDIT 2: Ok seems to work with the origin install too, after replacing / adding all the exe and mod files and creating custom exe shortcut (doesnt start from the normal shortcut). dunno if some servers would kick you or something. Can you add any info tuia? I don't actually know what I'm doing...