wulfbindewald

Members
  • Content Count

    177
  • Joined

  • Last visited

Community Reputation

5 Neutral

About wulfbindewald

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    near EDDW

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Update: I deinstalled and reinstalled the fixer 4.0 again and the cloud shadows 2.0 could be installed afterwards too. Prob solved.
  2. Hi Steve, the installation on my FSX SP1 SP2 failed. Even a first cloud shadows deinstallation from the control panel and re-install failed again, see the alert below. Any advise? Wulf
  3. wulfbindewald

    KSTS from ORBX

    Here again and FSX DX10+fixer related. I checked the relevant "fx_Orbx_KSTS_white_approach.fx" file in the Effects folder. There is a further mistake included in this file, because the relevant designated texture is called "Texture=fx_2_orbx_PAHO.bmp" and not ...KSTS.bmp. I guess the developer has forgotten to replace the content from another adopted and existing ORBX scenery. To make it quite simple: Please copy the existing "fx_2_orbx_KSTS.bmp" file 1:1 again into the Effects/texture folder and rename this one "fx_2_orbx_PAHO.bmp". Please let us know if this cured the prob. (The alternative is to carefully rename all entries ..PAHO.. to ..KSTS.. within the "fx_Orbx_KSTS_white_approach.fx" file. I do not recommend this proc). This has been already discussed in the ORBX forum (in 2015), but unfortunately there is no KSTS airport scenery update.
  4. wulfbindewald

    KSTS from ORBX

    May I jump in. I remember that there is a texture file "fx_2_orbx_KSTS.bmp" misplaced in the Effects folder. Please go into the FSX/Effects folder and shift (or copy and paste) this file into the FSX/Effects/texture folder. This should hopefully do the trick.
  5. The DX10Controller.exe file exclusion within the AVIRA tool (->settings ->PC-security ->exception) and the fixer re-installation afterwards again did the trick. Thanks for the hint!
  6. Hi Steve, there is a problem with the DX10Controller.exe file, downloaded within the fixer 3.4 version (Filghtsimstore.com): The antivirus tool AVIRA diagnostics a prob "HEUR/APC (Cloud)" within this file and therefore cuts and posts this file into the antivirus-tool quarantine zone. A relocation later from there to the original file location in the DX10SceneryFixer folder is not possible due to several folder security restrictions from the author. So I have installed the DX10 fixer but I can not use the controller. How to get rid of this "HEUR/APC (Cloud)" prob? A complete fixer+clouds reinstallation did not help. I think an AVIRA switch off is not good.... Wulf
  7. I´m not sure, if this helps. But I would give him a try.
  8. Today I was able again to go to my flightsimstore.com account & download section.
  9. Yes, the Orbx black boxes will be fixed too.
  10. Hi there, some overhead panel switches from the FSX A321 default VC are partially lighting weird at day and sunlight. Any chance to get this corrected with the fixer? Which fixer settings to be changed? The legacy slider to the right (aircraft) does not help. I´m using the fixer 3.3.
  11. wulfbindewald

    Registry entries FSX and FSX SE

    Not found anything additional relating to any simulator. Name of folder to be looked at for example?
  12. wulfbindewald

    Registry entries FSX and FSX SE

    Thanks for interest and help. This is what I see in the registry, pls see pic. The FSX SE path surprisingly directs to my FSX, although I do not have FSX SE. I wonder which SW might create this link, but as I learnt not the fixer. Wulf
  13. I wonder why there are entries for Flight Simulator 10.0 and Flight Simulator - Steam Edition 10.0 in my registry. I never had FSX SE, only FSX. Does the DX10 fixer install a dummy registration for FSX SE for any reason? Not complaining - just a question. (FSX DX10 fixer V1.8) Wulf
  14. Hi there, I observed since a couple of time that the ground shadows are ticked from some user, maybe unadvertently due to the "shadows" naming, although this option is strongly recommended not be activated. Why not to include a warning message into the DX10 Diagnostics? Wulf
  15. Thanks Steve, I use std. shadow settings in the CS menu. No metar is an option, but not really preferable. So I hope that you get the runway brightness issue sorted out..... Wulf