#1 2020-11-04 19:52:36

Anna Nym
FakeNickAdmin
Germany
Reputation: +379
Registered: 2012-10-10
Posts: 474
Windows 10 Firefox 82.0

BF42_win10_Graphic

hi @ all,

at some point I had to replace the 6 year old system.
Now I have a Win10 installation instead of win7.
I was also able to fix small problems with the display in connection with the New Saphire xt 5000series.
But ... the scale of the vehicles is strange - they are somehow shortened, everything else is very good so far. If this is already known, is there is a solution ... except for Win7 again ????


Thx  Anna

Last edited by Anna Nym (2020-11-04 19:52:49)

Offline

    Positive reputation 0   Negative reputation 1

#2 2020-12-23 20:58:50

DrOnzzER
Member
India
Reputation: +4
Location: India
Registered: 2012-09-30
Posts: 231
Windows 10 Chrome 87.0

Re: BF42_win10_Graphic

Try this if this helps:
https://team-simple.org/download/
Battlefield 1942 v1.612 Retail executable patched

Offline

    Positive reputation 0   Negative reputation 0

#3 2020-12-23 21:11:42

Trench
Member
United States
Reputation: +130
Registered: 2014-05-05
Posts: 221
Windows 10 Chrome 87.0

Re: BF42_win10_Graphic

Agreed with DrOnzzER, and the specific reason being that this updated BF1942.EXE includes "the widescreen fix."  Which just really means it allows selection of the resolutions your video card actually supports, rather than a hard-coded list decided by EA.  Any time you're picking a resolution that isn't one of your video card's and/or monitor's native resolutions, your video card and/or your monitor may indeed be "squishing" or stretching your perspective.

It's likely just "new install and different video card" leading to this change, rather than "specifically Windows 10", and you would have to solve it even with this same hardware under Windows 7.

I know some people felt the need to adjust renderer.fieldOfView in their videodefault.con once they went wide-screen, but I don't believe this really involves or resolves any "sqishing" or stretching.  Just "how far back is the camera placed", so to speak.

Offline

    Positive reputation 2   Negative reputation 0

#4 2020-12-23 22:04:39

llzkk
Player
Reputation: +46
Registered: 2020-07-19
Posts: 76
Windows 10 Firefox 84.0

Re: BF42_win10_Graphic

Trench wrote:

(...)
I know some people felt the need to adjust renderer.fieldOfView in their videodefault.con once they went wide-screen, but I don't believe this really involves or resolves any "sqishing" or stretching.  Just "how far back is the camera placed", so to speak.

I might also add that changing FOV can even lead to graphics bugs, so it would be better to leave the original value. The widescreen version has a built-in anti-stretch fix anyway, so I guess modifying FOV isn't necessary smile

Same resolutions (FHD without and with widescreen fix):
scr1
scr2

But anyway, I can agree that some rare problems may require unusual solutions smile

Offline

    Positive reputation 1   Negative reputation 0

#5 2020-12-23 23:24:32

s/w
Player
Reputation: +805
Registered: 2017-01-02
Posts: 532
Windows 10 Chrome 87.0

Re: BF42_win10_Graphic

FoV may lead to some graphical issues, but if you set it over 1.4, I think.

I've once set the FoV to something around 1.5 for a test, and the right-click zoom-in animation  was reversed.

Sometimes it would even reverse the whole map.

I keep mine at 1.1 , 1.0 (default) gives me a headache lol.

It's also worth noting that the higher the FoV, the quicker the objects will disappear from the camera. This is especially bad for dogfighting because when you switch the cameras, the enemy plane will disappear too quickly.

Values between 1.1 and 1.25 are generally ok.

Offline

    Positive reputation 1   Negative reputation 0

Board footer