You are not logged in.
Sorry to hear that Zwarrior I've only pointed out that messing with system files can be dangerous to user's PC, while putting modified DLLs in main game's folder can affect this game, nothing else. This is how programs (and mods) like this work.
Moving on to your problem, maybe this DLL doesn't work well with the game (in your case), so it's worth trying another one, as it was in my case, e.g. D3D8to9 didn't help me but other fix helped.
I've already discussed a similar topic here on the forum, so if you want, I can send you a link to it
Last edited by llzkk (2021-02-23 16:33:23)
Sorry to hear that Zwarrior I've only pointed out that messing with system files can be dangerous to user's PC, while putting modified DLLs in main game's folder can affect this game, nothing else. This is how programs (and mods) like this work.
Moving on to your problem, maybe this DLL doesn't work well with the game (in your case), so it's worth trying another one, as it was in my case, e.g. D3D8to9 didn't help me but other fix helped.
I've already discussed a similar topic here on the forum, so if you want, I can send you a link to it
i know you tried to help, thanks. Maybe Microsoft will end up fixing it, i hope.
This dll might be blocked by the TrustedInstaller. It's possible to rename the old dll-file and copy another one there with Unlocker.
https://cloud.mail.ru/public/jZuV/M3zapjtbt
Or from another OS.
You many need to restart your computer afterwards and maybe register another dll with:
regsvr32 C:\Windows\SysWOW64\%name%.dll
P.S. Acry's solution doesn't work for me. I had to reinstall DirectX afterwards.
I don't think that replacing DLLs in main Windows folder is a good idea. Just don't touch anything here, because it may lead to system damage. The better solution is to put modified DLL in main Battlefield 1942 folder (where bf1942.exe is) and everything should be fine.
I agree with that. It's not desirable, nor should it be necessary. But someone who has the issue needs to be the one to test and ensure an alternative actually works.
For a legacy application like BF1942.EXE, Windows should be defaulting to "I will be happy to load a standard Windows DLL from the local program directory." That is not how current versions of Windows normally behave by default, or would behave with a different or more modern application. This legacy behavior of "start with the application directory when loading DLLs" was replaced with a default of "start with the SYSTEM32 folder", as a better default security posture to keep rogue DLLs from getting loaded too easily.
Once you've dropped the DirectX 8 interface DLL into the Battlefield 1942 game folder, launch the game and then use Microsoft's Process Explorer to confirm that the copy of the DirectX 8 interface DLL actually being loaded by the BF1942.EXE process is the one from the game folder, and not the one from the SYSTEM32/SYSWOW64 folder.
If it's still loading the one from the SYSTEM32/SYSWOW64 folder, we might be able to come up with a .config file that lets Windows know what our intentions are here.
But I think it already works by default on this old game, because I'm currently replacing the Winsock interface DLL that BF1942 is using, by dropping a replacement into the Battlefield 1942 game folder.
i´ve tried that and it showed some "blurred lines" that moved from upside the screen to the bottom i tried to record it but those lines does not appear in the video
What you saw was screen tearing, so vsync is disabled as it should be. Now, all you need to do is change FPS cap from 60 to 100 (or more if you like, but I believe 100 is a default value in BF), and those tearing lines will be pretty much gone.
Just add "renderer.lockfps 100" line into your ...Battlefield 1942\Mods\bf1942\Settings\VideoDefault.con file.
...
Just tested BF with d3d8.dll only in the game folder. It works.
i have a doubt ¿Does this thing also affects other games like battlefield 4? ¿Maybe if i upload a video of it you could tell me?
Last edited by Zwarrior (2021-02-24 13:02:45)
suspicious activity here.. DLL's and stuff, I don't know about this
@Zwarrior
(This is a pic from 000.) If you had mismatched lines like these:
It's screen-tearing. (although, this is an extreme example.)
This happens when the FPS are not synchronized to your monitor's refresh-rate.
This also happens all the time, in any game.
However, the higher your refresh-rate is, the less noticable they become. But they will always be there, unless you enable a frame synchronizer like Vsync (worst kind) nVidia g-sync, AMD free-sync, etc.
But on the other side, enabling any frame synchronizer, will result in extra input-lag.
Enabling max FPS will allow you to have the least amount of input-lag.
If you have a 60 hz monitor, cap the fps around 200-350 and see if it continues.
...
You could try a multiple Refreshrate of your Monitor -2 HZ
For a 60 Hz means 238 as example.
But, ... the minimum FPS in game should not be lower then the chosen RefreshRate.
...
On the otherside Bf1942 is a Diva.
Sometimes it feels better with unlimited Fps. Specially if you have a 144+ Hz Monitor.
...
suspicious activity here.. DLL's and stuff, I don't know about this
That one was good
...
Last edited by Arkos (2021-02-24 21:13:49)
Specially if you have a 144+ Hz Monitor.
I've got the new PC parts on new years, and one of them was a 144hz monitor.
It has a VA display panel, so the speed isn't the greatest. But I wanted it for the superior contrast.
Anyways, the very first thing i've noticed, is how clear the picture managed to stay with rapid-movement.
When I fly planes, the ground almost looks ''static'' because of how stable the image is. I was so much used to the stuttering at high-speed with a standard 60 hz monitor that it felt strange.
Now switching back to 60 from 144 is unbearable lol.
Last edited by s/w (2021-02-24 21:46:06)
i have a doubt ¿Does this thing also affects other games like battlefield 4?
Yeah, it does.
https://answers.ea.com/t5/Battlefield-4 … -p/5584022
You can try disabling full screen optimizations.
Right Click on the Executable File (.exe) and Select Properties
Select the Compatibility Tab
Under Settings – Select “Disable Fullscreen Optimizations”
Click Apply
the difference is like night and day there lol, thank you so much Raklez
...
There was a Problem with an Microsoft Update which affected most PC's with mVidia Cards.
Stutters, Crashes, Framedrops, bad performance or BSOD
(The Fix will be automaticly installed in Windows 10 2004, 20H2, 21H1 - / Other Windows 10 Version i do not know, otherwise fix it manually).
English > https://borncity.com/win/2021/04/26/win … il-update/
German > https://www.borncity.com/blog/2021/04/2 … il-update/
...
Last edited by Arkos (2021-05-17 21:51:33)