I've been flying in EAW with MrJelly and ShoGun for a few years now in UAW160. I currently use nGlide on my Win10 as it seems to give the best screen size and FPS. I have tried playing around a bit with DXwnd but the screen was smaller and my FPS still struggled to be above 30-35.
The reason why I am tempted to find a DirectX solution is that in Glide, some aircraft just look strange/bad/half invisible etc. Here is an example of B5N2s from the Pacific Air War & FAA Avenger PS.
Is there a solution to this? Is it just a color palett thing or something more difficult to fix? I am willing to potentially learn if the programs/learning curve isn't super steep.
Thank you all for helping keep this combat simulator alive and working.
There is this section from Mosi's skinning tutorial:
However, given that it is impossible/impractical to make recent aircraft models fully compliant with Glide, would it be useful to compile a list of less recent models which are Glide-compliant?
I was referring to the problem of reversed textures, mostly on the wings.
I found a work around to this when the extra 3dz files were incorporated by splitting the wings horizontally. I did it on the
F2a Buffalo and it seemed to be successful but that's the only plane modified as such.
Well, it's never a problem I have worked on or looked closely into.
In his skinning tutorial Mosi seemed to think it was a matter of certain colour definitions in the pallette which caused problems with Glide, especially the large number of pallette slots dedicated to transparencies.
He seems to suggest that problems with glide could be avoided by sticking with the original pallettes and avoiding the pallette numbers used as transparencies. Generally - don't use custom pallettes.
For instance, the winter camo on many of the Eastern Front aircraft. I convert the summer skins to Gray Scale, lighten them a bit with the brightness function and then cut the pieces from the modified texture back to the original texture.
I also change one or two colors in the pallets all the time. The whitest color in most of the textures I come across isn't white enough so I edit one color to make it as white as possible. Same goes for some of the reds and blues.
Maybe that's what the OP is seeing. I can't tell 'cuz I don't do Glide.
I did a test by copying a UAW160 folder to an internal drive and running a host only multiplayer mission.
The mission was an intercept.
When I used my Windows 10 drive with the ini set at 1024x768 the best frame rate was 20 fps.
It dropped as soon as the enemy aircraft came into view, and even at 20 fps there was a slight stuttering that made it more difficult to register shots on target.
I repeated exactly the same mission with my Win 7 drive in. The frame rate was in the high 50s, and occasionally touched 60 which is the max that my card supports. Even at my default monitor resolution of 1920x1080 I was getting rates in the low 50s. There was little loss when the bombers came into view.
There is also a noticeable loss in Winows 10 when you fly close to the deck making ground objects come into play.
It is particularly an issue in multiplayer, which CaptJ and I are flying, hence his original query.
Just out of interest I set the GoG 1.28 system up again.
Flying with the 1024x768 screen I was getting frame rates in the high 50s and even up to 64.
Trying again in 1920x1080 I was getting the low 30s but occasionally up to 45 fps.
Might it be possible to negotiate with GoG to see if they can speed up 160?
