MarkEAW

I've used some new and old info to complete this new page on my web site. Its a performance record. Of my test of EAW. I haven't recorded anything for v1.2 as it does not have a Frames counter, so I'll have to use an nvidia program to give me results overall. I have used the un official versions,. I use v1.28 a lot, both GoG(w/wrapper) and without a Wrapper, both in DX3D mode. Here's most of my tests currently: https://eaw.neocities.org/performance.html Anyhow if your interested in posting your results I'd be glad to see them. I'm going to ask them to be for a certain version of EAW and one resolution, as this is best to get everyone's results. (see Help Doc)

Digging the 16 plane count and the extra squads increasing that. Why you think they only had 12 planes in the stock game?

FOG Support Development Doc: https://developer.download.nvidia.com/assets/gamedev/docs/Fog2.pdf I ran into this years ago too. This mentions how DirectX7 supports it as well. Seems to include a lot of detail, includes the W Fog info Z Fog ,Table pixel Fog and Vertex Fog. Indicates which old RIVA cards supported fog..... Most of it is over my head. just thought I post it before I delete the link. heh.

I'll post a link in the EAWPRO Club for a wrapper configuration file used only for EAWPRO latest release.....see you over there.

No promises is what I live by :) lol. Well not totally true, but with EAW and figuring whats up with it today, is exhausting. :) Alright well I know I haven't kept details of your mentioned changes on public forums in the past year or two. I was disengaged from EAW almost 98% of the time then. okay. Well see you on another thread later? :) I think we figured it out, well me mostly ;) If you didn't give it a try on win10, i would have left ithe crashing issue alone for alot longer...but i jumped right back when you gave feedback. Your welcome. (Now I have to explore more things in EAWPRO)....

Hey, When I click to run eaw.exe in EAWPRO Basic (the latest version and the previous version), it will now open, black screen, then closes, won't run. Win10 doesn't even write a compatibility reg entry for it, and the eaw.ini file does not get written either. and since the older version loaded before, I think its my system only...or win10 only. All other EAW games load and run...just not EAWPRO. Maybe a corrupt file?? So I manually added the primary comp reg entry to the registry. It didn't help. I think eaw.exe is closing before Win10 can try to even load a screen. I tried other exe Properties and doubled check windows settings for eaw.exe in its database, alll seemed fine, but its just not running.

I updated the FXEXE Patches Help Document with new troubleshooting instructions. https://eaw.neocities.org/fxexe-patches.html Should i add to this doc/update it with something else too? Thanks VBH!!

Yeah, CD Check....not sure. I know there's a database on windows with settings=fixes and modes that eaw.exe iis configured for. One of those is something about replacing the eaw.exe from the CD if something was wrong with it. However it doesn't have a way that I know of to know which eaw.exe is being used since all have the same name and company name (except the gog) release. They didn't bother with CRC checking the eaw.exe for any official version in the compatibility database. (opens with ACT toolkit). I'll keep any eye on that until hopefully sometime , I'll figure it out. So anyhow......WinVista and up have this Exploit Protection setting, I think Vista defaults to ON while Win10 is off. I had turned mine on again a few months ago :( oops. But I think your issue was, since your brothers Win10 system loaded upto the flight screen and crashed, and also the controls where greyed out....probably except keyboard. it kicked the game out. I think this is the Direct Input not working correctly and or a Joystick needs to be plugged in. So I hooked DirectInput and selected virtual Joystick in the wrapper and selected keyboard again for flight controls in eaw. Otherwise since the virtual stick is not there it kept firing..setting to keyboard fixed it. Anyhow. It has fog support!! Finally I did mention that before.:)

Alright well, one setting was preventing the game from loading. Something called "Force Randomization of Images" Something about stripped images can't run with that on or something. So 1 system override, I see other programs have the same thing....and override for this one setting. Anyhow, I wonder how the setting correlates with eawpro?? and not the stock eaw.exe.

I'm digging the "targeting sight" when i move the mouse. and the indicator on it when i push one of the buttons on the mouse..... Also flames out of the guns, from cockpit view. :)

Okay, guess what, Its running fine now. I turned off all the Security for eaw.exe under Windows Security>App and Browser Control>Exploit Protection. I have 23 overrides. I configured your game exe and folder path I think to just ignore all the system settings and it ran to the flight screen and locked up and crashed....ha ha haaaa..... I then remembered something about your game needed a joystick so in the wrapper program I checked virtual joystick on and the flight screen loaded up fine and played. I had to Hook direct input first. I'm using the DXWnD Wrapper for fog supported gaming and high performance fps. I can send you my config file for the game settings in the wrapper. Now I have to narrow down which function/security settings I can turn back on and still run your game. :) ugh. and then determine other issues if any.

Glad you got too the flight screen!!! On Win10, I know if you place the game in the programs files sub folders on C drive (your main drive I guess) it will have key/controller issues. Because it moves or duplicates the eaw.ini into a Appdata folder under the user name on the C drive. Its in a hidden folder I think. I don't know for sure all the details, I've been running eaw under a 2nd drive to avoid any WindowsOS entanglements/security issues. But It could be something else too...... I recently disabled the UAC user account control on win10 just long enough to test out the eawpro, but no dice. Put it back on..... I also turned off DEP data execution protection on everything but windows os and services...still no luck. This one protects the system from incorrect use of memory i guess. What ever is going on my system, it sucks. Its like your exe is targeted....why would the other exes run natively or in a wrapper, and yours will not. Makes no sense that it ran perfectly before. I just can't remember the last time I ran eawpro. Could be a number of times in the last year as I only ran each type or version of EAW for performance tests and thrills. old Log files are long gone too, I cleaned out my system a few times since. Alright, oh I see them coming with the jacket now....... :|

I just tried running the nocd nocddevice exe you modified at a request. Back when you made it, that one for sure ran on win10 for me. However now it behaves just like the latest release from you, it crashes quick. I defiantly think its windows configuration/and/or/updates that stop it. Okay have a good morning anyhow :)

Yeah I too checked the read only. Except it stayed with read only off. I too am having the camera control greyed out, its on mouse but greyed out, so weird. To get around the graphic error and cd check i use the DXWnd wrapper...although all other eaw games run in win10 natively. Your efforts are welcomed, but you don't need to do this if you don't want to. to learn win10 on top of trying to get the game to run has to be painful. Up to you.

Event viewer and then windows logs, then application logs. You can use the little search for 'even viewer' on the task bar.

I found a FXEXE v1.0 archive, the earliest archive I have I think that resembles what I ran before for sure and its not running for me. Just to the main screen and what nots, no flight screen or single mission hangers etc.... So its defiantly something that MS updated in windows that's prevent the game from operating correctly. Just like you said. (or video card driver changes) Its just so weird, it won't run in a wrapper either. Aw well. Hopefully I'll figure something out, but I think its beyond me. Thanks again.

Thanks. I found some good settings in the DXWnd wrapper, hence why I provided my settings file. I also found out my machine had Virtualization enabled in the bios and it cut the frames per second down by about 15 frames(so 20fps I was getting) on top of the win10 system slow down. So I'm getting the 64 FPS in both wrapped 128 and 128gog again. Version 12 is way up there again.....I'd have to go back and see what the actual FPS are for it.

Yeah, sorry on my end too. I won't remove the DL. But perhaps put some kinda of notice next to it. I did everything I knew to get the game running. I'm not sure what's going on. I would hope you keep the thread going though, if it comes up again, so I can read about it. Thanks for EAWPRO VBH, it was interesting fun. :) and for those wondering, you should give it a try.

I dump the zip onto a 12 folder. I get the CD-ROM is required...I used Fake CD setting on the wrapper to load up to the main screen. I can configure the game. Crashes when I click quick launch or when I pick a plane.

I used the exe you sent..... It still crashes, but it gives the 7217 error now. So I ran it in the Wrapper and it crashes with no error there. However it got further as the wrapper loaded up the window frame for the game, but crashes there after. (I'm still trying to load it though with different and unusual settings) Regarding the pilot map addition; I've added that myself. (I can't go back as I deleted or replaced the previous archive with the new)

Sure, I'll try it. If I didn't already. maybe your version is different then what i have?? Thanks.....

I tried the INI file you sent(just realized its in my mail), no joy.

I was able to get a EAWPRO from 2018 or so to run. (The date comes from when I DL it, not file date) Although when I picked quick mission it crashed the game or if i went single mission and picked a plane it then crashed the game. So overall it seems my system now hates EAWPRO. I can't find anything to keep it going or go in the first place when it comes to the last version. I tried hard and all kinds of things, unless there's something going on with the display driver i got from MS a few days ago, I don't know. I'll eventually install from Nvidia next time.

Yup, did all that. I just plugged a joystick in, that didn't help. Its not getting in far enough to write its own ini file. Just black screen then closes. I'll see what I got of yours from before what you sent me and see if i can get it to run.

BTW if you need a DXW configuration file for EAW I can send it to you right now. Its the wrapper settings already setup for you. The best settings known at this point, for the DXWnd Wrapper listed in previous post above. I'll upload it to mediafire when I get a chance...then I'll link it here. (for stock EAWv1.2) https://www.mediafire.com/file/nr0y38shqwx3m1q/EAW12_%28Stock%29-DXWnd.zip/file There are a few settings in there that are not needed for unofficial versions of the game. Hence I can provide a separate .dxw file with pre made settings for another version....just let me know!