Hi!
I have just switched my GTX1060 to RTX3060, and now I am having a problem with EAW: start menu screen is monochrome, it flickers, I cannot see a mouse pointer and cannot go anywhere. I had the same trouble with 1060 and newer drivers too, but then I could roll back to 368.81 or 397.31, while with 3060 there is no longer such option.
What I tried so far:
- GOG version. It runs fine, but I am too fond of 1.28C features and just can't go back to plain old 1.2
- Installing 1.28c (as well as 28a or 28d) over GOG version. Start menu screen becomes usable, but it's the same story - screens are now in color, but they flicker again, and there is no pointer.
- Placing dxcfg.exe, dxcfg.ini and ddraw.dll from GOG into 1.28c install. Start menu becomes colorful, but, again - flickering and no mouse.
Is there anything else I can do to make my belowed 1.28c operational again?

I used this with good results
https://www.mediafire.com/file/2d6y4d98e9hebq1/MenuScreenColorFix-DirectDrawComp-Vistaand7.7z/file
And there's also a D3D windower program that Mr.Jelly can help you with
I believe they are for Win 7.I have no issues in Win 10

Thanks! Unfortunately I did use ddraw compatibility tool before, as an alternative to .bat which temporarily killed explorer, preventing garbled 2D screens in some old games. Yet, the problem seems to be of different nature with the newer drivers, so it does not work anymore.
D3D Windower is either ineffective, or I am not using it right...
I heard that earlier GOG version used to be 1.28, so they apparently did something to 1.28 exe too. If someone bought it from them before they switched to 1.2, I would very much appreciate if that someone e-mailed me the eaw.exe

Check out this thread re- the GoG 1.28 version:

https://SimHQ.com/forum/ubbthreads....rs-of-the-gog-release-of-eaw#Post4561875


....also this one for the d3dwindower settings:

https://SimHQ.com/forum/ubbthreads.php/ubb/showflat/Number/4514617/Searchpage/1/Main/423272/Words/%2Bd3dwindower/Search/true/my-d3dwindower-settings#Post4514617

Jel

Wow, I did use it wrong then - d3dwindower works, if used without global flag (green "play" button). Thank you!
BTW, I found GOG's 1.28 version, and it works too, out of the box, in fullscreen. However, it is plain 1.28, w/o subsequent letters or features.

Another question: when I manually enter 1920x1080 resolution in eaw.ini of GOG 1.2 version, it works just as intended - no aspect distortion, wider FOV that in normal 4:3 EAW. But when I try doing the same in 1.28 (gog or not), it is way too zoomed in on the gunsight. Is it possible to somehow run 1.28 in widescreen?

Is it possible to post screenies?
These are both the default Spitfire IX at 1920x1080 in the default ETO theatre

This is an EAW screenshot in 1.28c


This is a screen dump from GoG1.2

Paint would not load the EAW screenshot- maybe the routine in GoG1.2 does not cope with 1920x1080. However, in the game I hit the win 10 "print screen" key, loaded paint after exiting EAW, pasted it in and saved the picture as a JPG.
Basically I get exactly the same screen in UAW160 too, so I am curious about the "widescreen" picture

Oh, never mind - the resolution issue was nglide's fault. My regular 1.28 did not have horizon fog in d3d, so I used to run it in glide, while gog's was in d3d. So eventually I just applied dgVoodoo2, and now everything works like a charm: 1.28c in widescreen, proper native 4:3 menu screens, no flickering, no need for d3dwindower.

Good show Dornil !!

Good to hear, but I am just curious about "widescreen".
Do my screenies appear to be in widescreen to you?

Well, yes, they do - they are 1920x1080, there are no geometry distortions, there is wider FOV.