MarkEAW

I'll do some more tests in single player non random. However I do get a slight drop too 0 fps (non responsive) on the first main screen when the 160 loads up. Not sure if thats related to the other loading issue. Again just to make it clear, I'll be using DXWND wrapper, since win10 increased the delays of the loading screens I can't test it in plain 'native' compatibility to determine anything regarding this issue.

I forgot what this file was, I DL it a long time ago. I think its just v1.28 of some sort, and looks to be in french. I'd ask MrJelly what you need to download rather than use these files. Or just install stock 1.2 and get EAWPRO by VBH.

If your using some type of gaming keyboard, this maybe the issue. Try a standard keyboard. There are two help docs you can read. Joystick and Controls and Troubleshoot Help Docs at my web site. https://eaw.neocities.org/joystick-controls.html https://eaw.neocities.org/troubleshoot.html

Looks like 160 Special and 160 Foundation all do the same thing. It hangs but if the cache has loaded previously, it seems to load smoother. (less halting and more response) I notice the FPS drop to 0 on the loading screens when they become non responsive. It just must be loading all the eaw world and mission data thats keeping it from going through that screen with ease. I tried 1.26 sydbod and it loads quickly, no drops in fps during the loading screen. (the thread stays active). I didn't run it through Win10 because the loading of the flight screen is delayed 10 secs because of a Win10 change that MS put out, that you realized at one point. Thats why we or atl east me went with DXWND.

It happens each time with the 160 Foundation exe I have. (not sure at the moment which version or build of the exe it is) It doesn't seem to matter what parameters are used in single mission, then launch a quick mission. DXWND wrapper on Win10. I could try a broader range of test, but I'm sure I have tested it throughly. I even think I tested it in Win10 without a wrapper and it still happens. It becomes non responsive, then just before a CTD it becomes responsive and finishes loading the flight screen. (Rarly does it make it to a CTD, but enough times) Give me sometime to get back to you. Not sure if it will be later today or tomorrow.

View File Animated Mainscreen for EAWPRO & 1.x derivatives Animated EAW Main Screen. It can be used with all versions of EAW 1.x. By VBH Submitter MarkEAW Submitted 10/24/2018 Category EAW - Europen Air War  

VBH, can you get to these EAW downloads on CombatACE? https://combatace.com/files/category/413-eaw-europen-air-war/ Anyhow I think you have to post so much to gain ability to access them. Then you have a limit to what you can download/ upload I went through them all already. There just repacked files from the past put into archives. I never did get an answer from the User that repacks them. I uploaded it to CombatACE file downloads. I can ask to have it removed or replaced I guess if you want?

Are these modifiers effecting the difficulty settings? If I set 2, thats the EAWPRO default, but then theres the enhanced AI with the additional in game ACE skill level (4th new setting)....where would that put things?

I do. But already had them. Thanks for sharing. I think he had other gunsights that I couldn't download from the wayback machine cause the links where broken. They may have been newer or different than the MKIII versions. aw well. BTW I uploaded the 1.2NoOS version today. Its a good addition to the file collection but I have not tested it out. Since it only contains two or three changes that have been proven long ago, I assumed it worked. (but I know I shouldn't assume :) Just short on time.

I use v 1.2, EAWPRO and 160 foundation.

The older machines are kept, because the users are older. They really don't want to spend the money (or time in some cases) to update their computers. Hell I'm over the hill and I don't really want another computer, I may update mine again, but I really don't want to build a new system again. (but I may some day of course).

From my experience, a lot of people prefer the retro look and feel of the original game with the ease of the built in frontend, including the animations in hangers, and the atmospheric sounds and look. Atleast that's what I'm told in e-mail and I also read some posts too. 160 doesn't provide that anymore, but I still I understand the work that's gone into it the gameplay and game data. Sorry I'm going off topic VBH. I'm sure I know why Rotton wants to always challenge and drag on a null questions all the time. When he was banned at SimHQ it was nice for a month. Now I'm not attacking anybody, I'm just stating the obvious fact.

Alright VBH. Thanks for explaining to my lack of my understanding. I'll look at the new 1.2 patch you posted above

I thought I already addressed the issues your hinting at in the other thread about needing an additional programmer. So I'm baffled by this new thread of yours. But..... We know the main issue is getting the game to run natively without emulation or compatibility workarounds without problems. But as it stands it runs almost flawlessly with Wrappers and Compatibility Workarounds. these are either applied by us or by Windows OS. Some work together while other workarounds conflict.

neat stuff.

There are two new issues as of this year with Win10 and EAW. (Actually these issues came April 2018 and perhaps a month or two before) -The Frame rate is lower...(Lower than Win7) -The screen transitioning to the flight screen and back is extremely slow; (for the screen to change while the game loads or unloads textures and models, etc...) Its gone from a 2 sec screen switch up to 10 secs or more. (The Win10 April 2018 update did this). *Using the DXWND wrapper cures performance issues now that the Wrapper works correctly in Win10 (It didn't before with EAW correctly). FPS and Screen transitioning is fast again. Althought the plans apear to jitter slightly, like a little lag. *You can use EAW in Win10 'nativly' if you wish. See my EAW Help Site for usage.

Hey VBH. Good to see you over here again. I was lonely posting about my site. It just gets old after awhile when mostly that's all that's getting posted. lol Sorry to hear about your ban from SimHQ, it seems totally out of line and biased.

I guess no one is interested at this point in updating the games DX code and etc. We'll have to wait I guess, or not.

Volunteer Programmer Needed: The EAW community is in need of Volunteers to code updates for this Windows 95 designed game. It currently runs under legacy compatibility layers or fixes provided by WinXP , WinVista (and the newer modern Window OS's). In some situations an external Wrapper Program or Registry Fix is needed to run the game with out problems, or with reduced issues. These are major things that need to be improved to keep current EAW enthuses and to attract newbie's to stay. -DirectX version needs to go from DX5/6 to at least 9.0c/9_1 so modern drivers and hardware can be taken advantage of by the game and the video control panel settings will work. There is No Horizon Fog in D3D when using Nvidia Cards and there are lower Frames per second in DD/D3D performance in flight. -Add modern Hardware compatibility, primarily proper GPU usage. -Update the in-game 8-bit front-end of EAW to 32-bit. Right now it uses the old DirectDraw to display. Its faulty; the menu, map and briefing screens do not have perfect color, and at times are garbled (tearing), sometimes corrupt. -Memory management intended for Win95 seems CPU intensive rather than GPU. The fixed up compliable v1.2 source code is in a mixture of "C", "C++" and assembler. You can use Microsoft Visual Studio 6.0 (In WinXP) to work on and compile the code. A custom DX6 SDK (although the DX7 SDK should also work) can be used. There is no programmers available to update the code to issue hardware repairs to the game at this time. Not many of the current EAW source code users have looked for new programmers. A few old timer EAW enthuses have tried to find someone in the past , but no luck in the end. So I thought I'd re-mention it here. I'd personally, would like to see this before some of us pass on, either by them leaving the EAW community or by the older EAW users dyeing off. I wasn't put up to this, I just decided to see if there is really anyone willing and capable of doing these updates. Please contact if seriously interested at CombatACE or SimHQ forums.

Thats what I thought, since there's no settings for graphical enhancements, perhaps EAW would automatically detect what it supports and uses it. (that is if the hardware/video driver support it).

gerwin, thanks for your responses about the terms and the way stuff works. The one thing I don't know for sure it what type of graphical enhancements the game provides on its own, rather than Post processing. By the looks of it , Biliner filter is used. But I don't know if this is automatic or it must be set with a Wrapper Program or by the video control panel first for the game to activate that type of filtering pre post? Also MipMap seems to take the shimmer out of the distant terrain in glide mode. There are no options to turn on or off graphical enhancements. I assume they automatically turn on if the hardware/drivers support, yet IDK for sure. I would like to know a list of enhancements the game is capable of though, anyone know?

the d3d.dll was changed a few times, hacked once I think for v1.26 and then coded for v1.28c. Maybe something to do with the menu screens, but I'm not sure. Been awhile since I read the changes they made. PS, Thanks VBH for the info. Since the glide2x.dll was part of the Voodoo vid card drivers, you don't see those DLLs in the eaw directory. But you may if using some wrappers with eaw in glide mode. The Intel videos is limited as far as I know. I'm surprised it worked with yours without a wrapper, but maybe its win10 compatibility layers at work. You should see horizon fog with your Radeon Vid card too. I don't think it will show with the Intel chip in Direct3D. BTW, you don't want to use win2000 compatibility tab setting in Winxp. Winxp sp1 or sp2 and up has all the necceary compat layers/fixes. With the Tab setting you may loose joystick control.

Looks simple MrJelly :) But IDK...the 8bit code would probably get dumped, and be easier to code a new 32 bit front end reading the same game data. But who knows what would happen....!? What is the d3d.dll file for? or didn't anyone figure that out? (I know it was modified atleast at one point).

yes, it uses directx 6 (d3d and DD) or glide 2.43 for the flight screen. The menu screens are 8 bit color (256) and us directdraw to display. (They corrupt with color issues and tearing (garbled) on some of them.) This is the primary problem for just running the single eaw.exe exe (it uses a d3d.dll btw too, but I don't really know what for)