Jump to content
Sign in to follow this  
JaneyBananey

Flickering dark boxes in WOE - Windows 10, ENB patch with custom d3d9 and DDraw dll files.

Recommended Posts

Howdy y'all!

So, I installed Wings Over Europe via Steam, promptly updated it to the October 2008 patch, and fixed the stuttering by using the ENB patch for Skyrim (of all things). I also cribbed the DDraw.dll from the DgVoodoo install, which prevented the game crashing when pressing escape at the end of a mission. A couple of things to note here:

- The renderer indicated in the options menu is not ENB, but my GPU still. Despite this, the game runs perfectly fine.

- I turned the shadows down from Unlimited to High as I read on a forum post that this could help with z-fighting, but this did not solve the issue. I will turn it back up to Unlimited if it is all the same.

- There are absolutely no other graphical issues in the sim what so ever, no matter the aircraft, time of day, or weather.

The issue I am describing in the title appears like so in sim. I took three screenshots so you could see the way the dark boxes flicker on surfaces. It is not just aircraft, either, but also terrain. It seems to get culled in a circle as I turn my head with TrackIR:

img00003.thumb.jpg.878e7756f4605dfcc532acc6ec26a6f2.jpg

img00004.thumb.jpg.6da2c797a579767cc3aeb7ae942a29d7.jpg

img00005.thumb.jpg.4f0633045fe9e658f41d0eb31fe3da39.jpg

As you can see, my wingman gets periodically eaten by this weird black blob. I am at a loss as to how to fix it, and if it cannot be fixed, that's completely understandable given the Biblical age of the engine. Thanks in advance!

Edited by JaneyBananey

Share this post


Link to post
Share on other sites

STEAM+SKRYM+ENB+ZFIGHTING+TRACKIR + WIN10 +blablabliblo...by now you must be surprised that it works,

I once ran Strike Fighter P1 on OSX El Capitan through Wine and was very satisfied to be able to run the start menu...XD

I see that box as some defect of the patches you are running, in my opinion if you want something cleaner it is normal to Win 7 with the game installed directly...

Edited by PeacePuma

Share this post


Link to post
Share on other sites

Not the first time we've seen someone complain about issue with the Steam version. There's some belief that it's NOT quite the same as WoE from the 3rd wire site.

I'd dump that, and get SF2. THAT, at least runs fine on 7,10 & 11.

  • Like 1
  • Haha 1

Share this post


Link to post
Share on other sites
On 1/26/2023 at 1:51 AM, JaneyBananey said:

Howdy y'all!

So, I installed Wings Over Europe via Steam, promptly updated it to the October 2008 patch, and fixed the stuttering by using the ENB patch for Skyrim (of all things). I also cribbed the DDraw.dll from the DgVoodoo install, which prevented the game crashing when pressing escape at the end of a mission. A couple of things to note here:

- The renderer indicated in the options menu is not ENB, but my GPU still. Despite this, the game runs perfectly fine.

- I turned the shadows down from Unlimited to High as I read on a forum post that this could help with z-fighting, but this did not solve the issue. I will turn it back up to Unlimited if it is all the same.

- There are absolutely no other graphical issues in the sim what so ever, no matter the aircraft, time of day, or weather.

The issue I am describing in the title appears like so in sim. I took three screenshots so you could see the way the dark boxes flicker on surfaces. It is not just aircraft, either, but also terrain. It seems to get culled in a circle as I turn my head with TrackIR:

 

 

 

As you can see, my wingman gets periodically eaten by this weird black blob. I am at a loss as to how to fix it, and if it cannot be fixed, that's completely understandable given the Biblical age of the engine. Thanks in advance!

 

Keep in mind that SF1 series + Windows 10 = not a good match. Windows 10 doesn't like much this game engine. However SF1 series works well with Windows 7. That is the reason I had to...left my first LOVE, SF1 series ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By JamesWilson
      Hi everyone,
      I was wondering how to customize the numbers after your callsigns, since it always gives me the same ones.
      I think i managed somehow once, a bit of time ago, but now i forgot and have no idea how to.
      I'm not talking about how to customize the callsign name, but the unit number after it.
      As you can see in the Roster and in the picture under, i get "Fast Eagle 1-1" and "Fast Eagle 1-2"
      Here are some examples:


      The numbers on the tail, wing and nose numbers are customized, cause i managed how to change them, choosing them individually for each unit in the mission file by changing "AircraftNumber=" and typing the number, like "2" (as for 202). It doesn't change by typing the whole number tho, like 202 by typing 202, but it goes by typing the number that corresponds to the list of numbers you have. For example, In a list that goes from 200 to 400, you will have to type 10 to get 300. Here i just typed "2" and "7" since the list starts from 200


      IIRC, in the past i just used to type the Aircaft number just like that, and in-game i had the proper number after the callsign, like "Fast Eagle 102", not just the number displayed on the plane livery.
      How do i do? I'm pretty sure that it's possible to have "Fast Eagle 102" on my screen HUD and in the Roster
      Thanks in advance for helping me.
       
    • By JPMoney
      I’m flying an F-16I Sufa mod for Strike Fighters 2 Israel. I’ve modified the loadout ini file in an attempt to change the missile types and positions on the pylons. I’m having a consistent issue with the outer pylons (not the wingtip mounts, but the furthest pylons from the fuselage under the wings). I want these to carry one AMRAAM each, and as far as I can tell I have modified the loadout ini, the related missile object inis, and aircraft ini to be able to accommodate this. However, when I go to a single mission in-game and access the loadout screen, those outer pylons are always empty (no missiles). When I go to add missiles manually to these pylons, all AMRAAM types only are available in “4s” and not “2s.” So in other words it’s trying to mount 2 AMRAAMs on each pylon, which shouldn’t be possible (realistically), as these are set up for single missiles only. The F-16I ini file does have a relatively complex series of pylon rules, but I believe I have it set up to be able to mount AMRAAMs on these pylons, and I can’t find any setting in any file that would allow me to indicate there should only be the option to mount one missile per pylon in the loadout screen in game. I suspect a setting related to this “4 missiles” issue is preventing my loadout ini file from operating correctly and defaulting my vipers to have AMRAAMs on those pylons. 
       
      Any thoughts on a setting I am missing here?
    • By muhammad
      Hi everyone!
      after few miles of scrolling .INI files and testing everything on the game
      FINALY:
      " Cockpit Shadows " !!
      --!  enabling process is same for each plane  ! --
      --!  enabling process should apply on each plane you like to have cockpit shadows on 'em  ! --
      --!  Be Advised !: This "Cockpit Shadows" has some little BUGs so we all should work on it together to make it better  !-- 
      It's better than nothing :D
       
      * Q: How to enable Cockpit Shadows?
      - A: All you need to do is to make a .INI file with the same name and right at the place your chosen plane cockpit 3D file ( .LOD ) is located.
      Example: 
      !! [  Cockpit file are located at the folder with the same name (most of the times)  ] !!
      SHO to Viper team F-16 BLK 30 to act like a test plane 

      here the plane's Cockpit 3D model is the LOD file named " Cockpit_F-16C_B30.LOD " and above of that, our personally made .INI file;
      Now
      Inside the .INI file we should drop this :
       
      [Shadow]
      CastShadow=TRUE
      ShadowCastDist=5000
      MaxVisibleDistance=800 
      -------------------------------------------------
      * you are free to change the numbers  
      -------------------------------------------------
       
      here's an example file which you have to change it's name to the plane's cockpit file name !
      plane's cockpit file name.INI
       
      *with this simple trick you can enable shadows for every .LOD file.
      feel free to ask.
       
       alexis99 thanks for that little help
       
      sorry for bad English :)
      hope ya'll enjoy!
      one love.
       
       
      plane's cockpit file name.INI
    • By LaoHu
      I downloaded this mod for the F-5 and all of the skins for the aircraft are black, which means the textures aren't loading but I can't find out why it isn't loading. There is no exact installation instructions other than extract it into the mod folder which I did and there doesn't look like there are any issues with the file placement compared to the other aircraft files. Can anyone help me out?

      P.S. the drop tanks have the textures working and the cockpit, loading screen, menu, etc all work. Everything but the skin. 

       
    • By pearlharbor74
      Ok so in sf2 when i try to spawn ground vehicles with mission editor like an anti aircraft just any ground vehicle from mission editor it does not pop up inside the game once i load in not even on  the map it just like vanishes once i click accept from mission editor. Inside the mission editor i can spawn everything else without a problem planes/ships/ that stuff yk just cant spawn ground objects can someone pls help :)
      2023-02-25 02-20-56_Trim.mp4
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..