Hi guys,

I purchased the A2A Spitfire a while, and wholy recommend it if you don't have it, but I've had one little problem that has come up lately...

After returning to the Start screen, usually because I forget about the manual Hydraulic pump on landing, I'll find this strange thing in my startup box, when I re-click Fly Now! and reload the scenario, the entire visual model is present, but I cannot start the engine without using Ctrl-E

Anyone had this issue?

Jackson - would you post (cut 'n' paste) the [Graphics] section for your fsx.cfg, please?

Sure.

[GRAPHICS]

AC_SELF_SHADOW=1

AIRCRAFT_REFLECTIONS=1

AIRCRAFT_SHADOWS=1

ALLOW_SHADER_30=1

COCKPIT_HIGH_LOD=1

D3D10=0

EFFECTS_QUALITY=2

ForceFullScreenVSync=1

ForceWindowedVSync=1

GROUND_SHADOWS=0

HIGHMEMFIX=1

IMAGE_QUALITY=0

LANDING_LIGHTS=1

NUM_LIGHTS=8

See_Self=1

TEXTURE_MAX_LOAD=4096

TEXTURE_QUALITY=3

Text_Scroll=1

SHADER_CACHE_PRIMED_10=1693500672

SHADER_CACHE_PRIMED=1693500672

You have Bojote Shader Mod 3!

 

This is the issue with it ...

This Mod destroys many addons ...

Ok - great:

 

Insert this line into it and restart the sim...

 

SHADER_CACHE_VERSION=2012

Wendall,

 

I've never seen this issue reported, but, you may want to try re-loading your aircraft after loading it from the UI. FSX loads differently from the UI then from within the game.

 

Also, the not being able to start it w/o CTRL-E, almost sounds like a corrupt flight. You may want to try loading another flight, then load the Spitfire just to see if this issue is related to a corrupt flight.

 

I posted this link in our beta forum, so I may have some more suggestions a bit later.

 

EDIT:

Ah, you can see guenseli beat me to this post. Hopefully he nailed it.

 

Scott.

This will cause FSX to rebuild the Shader cache..

 

If the Shaders cache contents differ from the FSX root shaders folder or the WaterConstants.xml has been changed - the Shaders cache must either be deleted, or be rebuilt by changing their 'version' - as will happen providing he follows what I've posted.

I doubt that it is resolved with rebuilding shader cache, but of course, he could try ...

 

 

I have had this issue also long time ago and was only able to recover with my FSX vanilly backup.

Unfortunately I can't say how I get rid of it successfully at the end ...

Since your talking about the Shader, I have the FS Water Configurator, and used to use it, is it possible that is the culprit?

Yep - the two are not compatible. Personally Jackson - I took the Shaders 3.0 mod off the pc a while ago - didn't make sufficient difference to warrant the aggravation (using Nvidia). I do use the FSWC now, too. Nice little proggy. Just delete the ALLOW_SHADER_30=1 from the cfg. I would also delete the Shaders cache folder,

 

( The folders are located here:

 

%LocalAppData%\Microsoft\FSX\Shaders and %LocalAppData%\Microsoft\FSX\Shaders10 )

 

to guarantee that I've done all I could to remove the mod.

 

Cheers

Ok, so I have deleted ALLOW_SHADER_30=1 from my .cfg, and deleted the two files, and will do a test flight in a little bit...on the other hand, this video:

is shot and narrated by a guy who has NO experience in the Spit, and is trying to get it up in the air and flying...quite funny!

I had that issue as well with all my addon planes, it was from trying the Shader mod 3.0 and then uninstalling it (maybe I did not follow uninstall correctly), but yeah rebuilding the shader cache resolved it for me.

Ok, so I have deleted ALLOW_SHADER_30=1 from my .cfg, and deleted the two files, and will do a test flight in a little bit...on the other hand, this video: is shot and narrated by a guy who has NO experience in the Spit, and is trying to get it up in the air and flying...quite funny!

 

I actually watched the whole thing, quite funny.

Bringing this topic back because its happened again. I haven't installed anything new except for Accu-Feel, which doesn't make changes to any *.cfg files, correct? I was loading up a flight when a message box popped up saying "attempt to call a nil value". Everything was functional, but after I exited the flight, the glitched model showed back up again.