ares77

Yep that did it. Thanks. Does it do that with all programs? Because it automatically places everything in the (x86) folder by default.

Hmm does uninstalling it remove all the downloaded content as well? Or will it leave that where I can just transfer it all over? 40 something gigs is a lot to redo.

Windows 7 and its in Programs (x86) under WOV

Ok so I've had this little problem lately that is as of yet unsolved. http://forum.combatace.com/topic/55825-whats-wrong-with-this/ So I pretty much gave up on it since no one seems to know the answer. Well the other day I went to play. Game loaded up as usual. Went to play single mission and during the flight I noticed all my controls had been reset as if I just installed the game. Go reassign my controls like I had them before then head back to what I was doing but I noticed on the aircraft drop down that the very planes I couldn't get in the above mentioned post all show up now for the first time (all stock migs, OE Birddog etc) and fly fine with pits and all. Fast foreward today and poof they are all gone again. The one thing I noticed is that when I reassigned the controls the second time I had a few differences than the first time (ie O for open bombay doors at first and Ctrl+O the second time). Now all my controls are back to how I originally had them at first. It's almost like the game loaded up a fresh install then went back to the original yet I only have one install modded WOV 08 etc. Anyone care to take a stab at what is going on here? I'd love to get all my stock aircraft back.

Oops my bad thats a typo on here (can't edit it anymore). It's like you have it in the ini. WOV/08/ODS addon+ BTW I forgot to put that.

Really? What is it that 7 is having problems with, random bugs (like I am experiencing) or what? I have Win7 on mine, not trying to say "mine's working" type of smart ... but what I need to be on the look out for.

OK what do I have out of whack to where my stock migs aren't flyable. I know about the common knowledge about adding the A-4 pit and changing the ini's etc. I even have enough knowledge to swap pits and even used some downloaded ones on different planes. My AN-2, B52's, TU, B1's, F-111's (on my old comp when the F-111's didn't have a pit with them) etc I got all working no problems. A copy n paste from my Mig-17 folder. [AircraftData] AircraftFullName=MiG-17 Fresco-A AircraftDataFile=MIG-17_DATA.ini LoadoutFile=MIG-17_LOADOUT.ini CockpitDataFile=Mig17_COCKPIT.ini AvionicsDLL=Avionics60.dll AvionicsDataFilename=MiG_AVIONICS.INI [LOD001] Filename=MiG-17.lod Distance=100 [LOD002] Filename=MiG-17_lod002.lod Distance=250 [LOD003] Filename=MiG-17_lod003.lod Distance=500 [LOD004] Filename=MiG-17_lod004.lod Distance=1000 [LOD005] Filename=MiG-17_lod005.lod Distance=8000 [shadow] CastShadow=TRUE ShadowLOD=MiG-17_shadow.shd ShadowType=1 ShadowCastDist=10000 MaxVisibleDistance=150 [TextureSet001] Directory=VPAFmetal Name=VPAF Natural Metal Nation=NVietnam Squadron= Specular=1.000000 Glossiness=0.500000 Reflection=0.800000 [TextureSet002] Directory=VPAFSilver Name=VPAF Silver Nation=NVietnam Specular=1.000000 Glossiness=0.500000 I've tried it with and without the avionics files, All the spelling and upper/lower casses match the files exactly(went to rename folder and just copy/pasted it to ensure exact spelling in case my vision is deceiving me) and all the files listed are there as well. The pit folder and file I'm using is just one from the Mig 17's already working (the EAF one I think). Like I said tried just following the common knowledge, and even tried using the "Make mig's flyable" ini's as follows [AircraftData] AircraftFullName=MiG-17 Fresco-A AircraftDataFile=MiG-17_data.ini LoadoutFile=MiG-17_loadout.iniCockpitDataFile=A-4B_cockpit.ini Pulled every Mig-17 file from the object.cat and created another one just in case it still won't let me fly it. What am i missing here.

The best reason for a comp crashing is a reason to tell the wife you need a new one . Fortunately you were able to recover most of your stuff when mine died I lost everything.

Yes it's me again. And yes theres another question. The A-Team Skunkworks site, I keep getting the HTTP 501/505 message when trying to get to the forums to try and register. There's just a few more birds (B-17, Viggen and a couple more)I had on my old install that are not on this site anymore that I am trying to get yet cannot get to the forum to register to be able to get them. Do they take anymore requests, are they not active anymore or what. Anyone here associated with them that I could email to request assistance in this matter? Thanks. Even hitting the Donate tab produces a "Fatal Error".

Ahh didn't know there was more than one A-10A out there, thought as long as it was for the right series and model (A,B etc) then skins would work. Using the stock one from column5. Game is WOV (patched etc). Ya BMP's are completely different mapped so that's the problem it's for a different model.

Why do some aircraft (such as my A-10A) see some skins but not others reguardless if the info for the texture is added correctly in the A-10A.ini and it has the right files (bmp's, Texture,decal etc) in the folder. Looking at the bmp's theres 2 different types. If the add ons are mapped differently (by the maker)reguardless of whether the ini's are changed they show up white. Can the model only see one type? If so how do you change which mapping pattern to follow what section controls that?

I figured it out, (i think) The aircraftobject.ini was in objects folder and deleted it out. But it wasn't in the flight folder (if it was supposed to be there). Put it in the flight folder and it's working fine now.

As in through the options screen in game? Did that a couple times if that's what your talking about.

It recognizes the input fully on his other games. Jets like the F-4 With throttle set to max it will flicker between 80-82% on easy no more than 50 % on normal. I'll check the calibration settings next but I "think" that part is OK. Play Mechwarrior right after and it goes 100% like it's supposed to.

Update. Added ODS problem fixed.