hurricane3

I have FE1 and am running on W7 64 bit.I've found for some reason I can't drop bombs anymore.I tried the default command (enter) after selecting the bomb with the \ command but they won't drop.I tried assigning the fire/drop selected weapon to another key and also tried assigning the command to a joystick button ,but the bombs still won't drop.This is with all bomb carrying aircraft.It's as if the command no longer exists.Anyone have any ideas that aren't too involved ? Reinstalling isn't an option as I have far to many planes and mods installed. Another proplem while I'm at it is many planes ,even with the engine off, start off moving from the takeoff position with the speed building to around 45 kph before dropping back to 0.Not big problems but kind of annoying.

I don't know what either an AIRCRAFTCONTROLLIST.ini or an AIRCRAFTOBJECT.ini even is so I never modded either one on purpose.I have installed quite a few aircraft ,could just installing a new aircraft cause this?

I can select the weapon ok but the command to release the bomb (enter) doesn't work. I tried reassigning the command to another key or a button on my joystick ,still the bombs won't release.I tried deleteing the the default ini and letting it creat a new one but still the bombs won't release.As I said I don't remember if the bombs ever released in windows 7 ,so maybe this (along with the planes starting to move even at 0 throttle) is a windows 7 thing.

I can still select secondary weapons in flight but can't fire or drop them.The main guns fire otherwise I would have to try reinstalling the sim as it would be impossible to even try and dogfight.I wish I could remember if I could ever drop bombs in windows 7 ,I know they worked in xp.It's as if the command for fire or dropping bombs and secondary weapons never existed.

Thankyou for your reply .I already tried changing the command for dropping bombs (fire selected weapon)to "B" but no joy.I deleted the default ini but other than having to reset my controls the bombs still won't drop and the planes still start from the take off position, moving, as I said in my first post.As for the engine I intentionly (spelling) shut it down using the "control I" (engine toggle),prop is stopped and throttle is at 0, to see if that would stop the plane from moving but it still accelerates to around 45 kph before dropping back to 0.I have found moving the null to full left seems to help but not always. Looks like I'll just live with these small problems (I can always just say boom when I try and drop a bomb.)

I had to do a reinstall of First Eagles I and now when I hit the Esc.button to exit a mission the sim closes to desktop instead of just exiting the mission.The Esc. button works ok on any other screen but if I'am in a mission and want to say go back to the Hanger Screen I can't, the sim closes and I have to start all over again. Any ideas why ?The Esc is mapped to exit mission and can't be changed .Sometime if I can hit alt.Esc.very fast the sim will go back to the previous screen,but it doesn't always work.

YES, you did it! That even took care of the graphics problem.Thankyou so much ,your in the will!

Yep, after I got your post I went back to look just to be sure and those are the two ini files I looked at and nether one has anything about shaders.Also I just found out when in the Flanders terrain and I hit Esc ends the mission and just goes to the previous screen like it's supposed to do.And the plot thickens when going into both the Cambrai and Verdun terrain there is often a graphics problem when I pan to the right of the aircraft the ground loses it's texture.After I get airborne the graphic are ok.This only does it in the two terrain Cambri and Verdun ,the same two that when hitting Esc takes me out of the game.

The only texture file that had lines about shaders was the Flanders folder.The Verdun,and Cambrai folders ini's didn't have anything about shaders in their terrain folders

Nope, I went into the terrain files and changed every instance of UseEffectShader=true to false but it didn't change anything.I'am resigned to live with it now.

OK ,I changed the EXIT_GAME to ALT+E leaving the QUIT_GAME blank, so now hitting ALT+E takes me out of the game.

Wrench, there wasn't any ini files in the objects folder they are all dll files.I went ahead and backup the default ini then deleted it and went into the sim and flew a bit.Still the same, Esc takes me out of the game.I checked the new default ini and it still says EXIT FLIGHT=ESCAPE although now if I'am in any screen other than in a mission when I hit Esc I get the pop up menue in the upper left hand corner,so at least that's something.

A fast update ,I went to the controls section ,made a copy of it , then changed the first line from EXIT FLIGHT=ESCAPE to EXIT FLIGHT= ESC. When I hit the Esc button, while in a mission nothing happened.So next I tried changing it to Alt+Esc and nothing ,I tried just using the letter E and then it would take me out of the game like Esc did.So I give up. Thanks guys for trying to help but it seems like it's almost hard coded for EXIT FLIGHT = to mean exit game, instead of Exit Flight. Since the sim is already patched to the latest Expansion Pack and I have max188 terrain and a few planes I just put in, I'am not going to uninstall and reinstall I'll just live with it.Thanks guys for trying to help but it seems a lost cause

I still would like to know how two different commands do the same thing ,that is the Ctrl takes me out of the sim and Alt Q also takes me out of the game and the sim won't let me change either command.Go figure Also no command will just take me out of a mission.Go figure again

Regarding the plane moving when I go into the missions ,I found if I hit Ctrl+I to select engine I can stop the prop and the plane stops.

Always something,another problem I forgot to mention is when I go into the mission (where the planes are lined up on the field) 99% of the time my aircraft is moving.At times it starts out at 0 mph and goes to 4 to 10 mph ,other times it start right out at 15 to 20 mph, this is with the throttle reading 0.

I just realized that the Esc key and the Alt+Q command are doing the same thing.In other words hitting just Esc is supposed to just end the mission but still leave me in game and Alt+Q is supposed to take me out of the game, but they are both taking me out of the game.

The message is a game message not system message, and yes if I'am in say the loadout screen, and hit the Esc button it wil take me to the previous screen but if I'am flying a mission and hit Esc it shuts down the game back to desk top ( or in my case to the screen I have all my flight sim exe's on,just a folder on my desktop labeled flight sims).

I'am running both updated DX9c and DX11.Since only the Flanders terrain has an ini file that has anything shaders in it ,I guess that would be the one to backup and edit.Should I change the line that says "useEffectShader=true" to False?

It's installed on an external 2TB hd.I have UAC off and run my programs as admin. set to run in XP mode sp3.

When I tried to change the Esc key it says "can not map quit game key or mission end key"

The only terrain folder that had anything about shaders was the Flanders terrain.It had useEffectShader=True in all case,s where the line useEffectShader=.Since I don't really know what I'am doing I didn't want to change any thing and mess things up ,so I can live with the problem ,it's just one extra step that I have to do if I want to end the mission and go to the hanger or loadout screen.Thanks guys for the advice.

Sorry , I should have given more info.Yes I have the sim patched up to the last expansion pack ,so it's fully updated.I'am running Windows 7 64 bit and the last time I had the sim on this same computer, the Esc. button did what it was supposed to do.Other than Max188 terrain mod, the sim is still stock, I haven't as yet added any other planes or effects or missions but I will. The last time I had the sim installed I had it fully patched and had terrain effects ,missions and many planes installed and everything worked as advertised.

Ok, works now.

For some reason this link doesn't work for me.