eawpro flickering on win 7 64bit un playable also menu distorts inverts colors.

Menu color is an easy fix.
Flickering, try to default your Video control panel settings for your video card.

I did and nothing all that crap is off

try the DirectDraw Compat Fix
http://crappybitter.livejournal.com/29921.html

I think you run the program, then select eaw.exe and write to the registry or make a reg file and install it.
That should fix the colors.
Might fix flicker, but I didn't have flicker problems.


I don't know your other specs, like brand of video card?
You may need a Wrapper program. D3DWrapper......
https://www.fileplanet.com/archive/p-70607/D3DWindower-English-version

or use EAW in Glide mode, with nGlide wrapper installed

Hi flightsimer90s, welcome to EAW.

Your problems are caused by your videocard and drivers which don't support 256 color graphics and a 640 x 480 resolution, or one of the switches for your videocard settings in control panel is not recognised by EAW.

Go to your desktop setting in the videocard's control panel and check if it allows you to select the described setting of 640 x 480 and 256 colors for your desktop.. If you don't have that selection available then it's probably best to use one of the available videocard workarounds, like the DX wrapper or a Glide wrapper. You can find info on how to use them on Mark EAW's website, his suggestions may also do the trick.

When you do have this low resolution choice in your videocard panel, try switching everything to the lowest and fastest setting with as few selections active as possible, except the ones which turn down graphics. If you can make it work that way you can swtch the selections in again, one after another, and test which ones cause the these problems. You may still be able to play the game normally with what you have now, as the game itself runs in a different graphics mode then the startup and other screens.

Let us know how you fare, Ill keep an eye on this thread to see how you're doing and provide any advice if I can. BTW, being a NoCD, NoOS version EAWPRO needs a full install, preferrably a copy/paste of the game directly from the CD or any other location, which bypasses the creation of some registry entries and usually makes things a little easier.

VonBeerhofen

If you're using an nVidia card, try 4x Multisampling combined with 4x Sparse Grid Supersampling via nVidia Inspector.

working now was going crazy without joystick.

Don't think that's EAWPRO, looks more like v1.2 with some familiar looking sky, but I'm glad you're flying,
The real EAWPRO is only available from Mark EAW's helpsite:

https://eaw.neocities.org/fxexe-patches.html

VonBeerhofen

That must be 160 with the EAWPRO theather.

Oh, I didn't know there was such a version. I've only been aware of an OAWPRO version, which caused quite a stirr. Why should such a "superior" version need to have such an "inferior" version incorporated? (That is unnecessarily rude and is not in keeping with our efforts at keeping things collegial and civil. Don’t do that. It starts the ball rolling. I am getting more inclined to not discuss and more inclined to just start suspending. That would be a shame since it would negatively affect the continued running of this site.) To be honoust, I have no idea what it is without knowing where it came from and what's in it, but if at all it's one of the above it's quite obsolete by now and will be missing some important bugfixes.

If however it's an earlier v1.2 derivative, like FXEXE or v1.28, or just a modded v1.2, then it's a good start to get acquainted with the game. EAWPRO is by now a pretty tough game and not for the squeemish. I know there was an FXEXE going around with Dumoulin's name in the EAW.INI, possibly used a short time with 352nd after he quit RAF_17th. Can't stop the blood from running where it's not supposed to go.

As I've tried to explain before, incorporating EAWPRO into anything is a useless effort since changes are following each other up quite rapidly. All it needs is a minor change to some file format to cause havoc and I can't promise that such will not happen at some point. Such multiple versions also make it a lot harder to help people, I can't help with older versions or incorporated ones since I have no idea about what was changed or what's in that old version and what not, and I don't wanna know either.

Support is only for the current version at your website plus the Beta versions being tested by some helpfull pilots without who'se help EAWPRO may not even have been possible, so thanks a lot guys!

VonBeerhofen

Jel likes to make all EAW version available so he does his best to incorporate them into the 1.6 package. Most work but a few don't and he's open and honest about why something doesn't work.

There is no nefarious scheme and I think everyone should be happy with his efforts.

There's no mention of a "nefarious" scheme, there's only mention of several people distributing my work for whatever reason, which isn't going to be of much help as this particular case proofs. It's happened before that Mr.Jelly gave wrong instructions on EAWPRO's install and I've never seen the guy again after that. Such things should simply not happen. It's my creation, let me deal with it as I've always let you guys deal with v1.60's problems.

VonBeerhofen

Look, the arguments between the two methods, 1.6 and EAWPro, are getting tiresome. Not just tiresome, they are damaging the overall status EAW and is causing two armed camps.

Good work is being done in both. There are good things to be adopted from both. Incompatibilities between them are sure to happen. Wouldn’t it be better to resolve problems than snipe at each other ?

Users who come in here are sure to be both confused and turned off with the squabbling.

VBH asked Jel not to do that in the past, but he did it again despite what VBH was told he removed it. But Jel did it again.
Its an intentional thing and I clearly see that.

Even though I think its a neat idea to include EAWPRO into 160, its not at all complete and doesn't do EAWPRO justice . and its against VBH original wishes.

If this guy truly had a problem with EAWPRO flickering and wasn't setup to ask for help with EAWPRO, we could have saved me the headache too. 160 has its own issues and should not be confused with EAWPRO.

Ugh.

Meaning what ? That does nothing to help.

OG, I promised you to stay out of any threads created by Mr. Jelly or Rotton, and I have kept that promise, unless EAWPRO was somehow dragged down. I can also promise not to mention the word v1.60, as long as others don't mention EAWPRO and refrain from any claims of superiority and just tell the community what's new.

I believe there's no difference in the ammount of work entered in either version and that each is very different. It should be a good thing and not be a reason for hostillity. Once again I apollogise if I stepped on someone's toes, I know I did and I'm sorry but I was equally hurt.

I want to be able to do my thing in peace and harmony, which I think is possible if we forget the past and let bygones be bygones and respect each version equally as being just an effort to keep this community amused and not an effort to be superior. You can still make it as good as you can without such claims.

It's up to the community to decide what they like and there's no reason why they couldn't like both equally well. They're well capable of making up their own minds without anyone trying to influence their choice.

I can not offer any help with what the others are doing, I need that energy for myself and I'm also not willing to discuss with anyone what I do or how and why I do it. I do not expect anyone's help either, keep that energy to yourself and concentrate on your own stuff, a discussion is simply not going to happen so don't even try to start one.

Help the people who need your help and let me help the people who need my help, it's not too much to ask for is it? It's all I have to offer and I think it's a fair offer.

VonBeerhofen

Sorry VBH, I was tired and didn't have much time to post. So everything came out a bit odd. Teach me to post in a hurry.

About the so call flicker issue and color issues; I wanted to help this guy but he was vague to start off with I did my best with what he offered of his problem. Which he was misleading.
Anyhow fun times.

No mention by the original poster if his color issue was fixed in the menus. I think from now on I'll just point out my help site link. lol

Ugh is used in writing to represent the sound that people make if they think something is unpleasant.

Don’t be coy. That bit was wasted. What was your ugh directed at ?

Mark please check your facts before making statements like that.

I considered that the FXExe/EAWPro install was untidy, due to the number of files in the root folder.
So sometime ago I produced an installation which was tidier and set up for OAW users.
I made it available for OAW users via MediaFire.
VBH asked me to remove it, and I did. It has never been replaced.

If you check my folders at MediaFire there is no installation of the FXExe or EAWPro available.

The only thing that is there relating to EAWPro is a theatre folder download of the EAWPro theatre for 160.
This is clearly announced in the "160 Rationalisation and Installation" sticky, along with with the rationale for its existence:

EAWPro theatre

The download link has been there since November 27th 2018, and as far as I know nobody has raised any issues about it.