ares77

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.

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 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.

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.

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".

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.

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?

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.

Yes its me again, having throttle problems out of my son's install this time. With throttle full foreward it won't apply more than 50%. Joystick works fine on other games. His install is WOV, patched to 08. Weapons pack gold installed, WOV Air Ground expansion pack installed. The aircraft object ini was in the objects folder so it was removed but it didn't stop the problem. Where should I be looking now.

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.

I have WOV patched to 08. Many add-ons etc. I added on one of the sound add-ons and like most of them except some of the prop sounds on some of the aircraft such as the AC123/130 AH1 etc. They sound sped up and I don't like them. Checking the Data.ini's on each the correct sounds are there in the files pointing to the correct sounds in the sounds folder but the AH1 sounds like the ME109's high pitched whine that I don't want for this aircraft nor the AC's Haven't even got around to the B29 mustang etc etc. yet. What is changed to alter the sound other than the enginesoundname=A1engine in the Data and the correct coresponding A1engine in the sounds folder. I don't remember what was changed so I don't know what file from my backup to replace.

Update. Added ODS problem fixed.

First off thanks for the helpand patience this is frustrating. Ok I did that. Took a fresh A1 engine sound renamed it to R3550 in the sounds folder. Data ini is copy n pasted straight from data ini. [sound] EngineSoundName=R3350 AfterburnerSoundName= DamagedEngineSound= FlapsSoundName=Flaps AirbrakesSoundName=Airbrakes GearsSound=Gear Same thing. Sounds nothing like it no matter what RPM the engine is at. Messed around with the sound list doing the same which caused no engine sound at all so I changed it back. Even played with the J79 sound and changed the data to use it. Sounded fine. No matter what prop sound I use it ignores it. Tried them all, renamed and tried again. Every other sound it uses fine though. Prop sounds it wants to ignore and pitch them up. So far it's like that on every prop job. Damn C-130's sound like buzzing flies rather than the deep sounding stock ones. The radial one sounds alright so If I can't figure it out I'm going to use it. Would just rather use the stock A1 sound if I can figure this out.

I just went through all my sound files one by one and whatever sound it's using it's not located in the sound files. Just replaced the AH1 Data ini with my backed up one as well as the lods (didn't know if it would do anything just in case). Went to the sounds list ini in the flight folder and changed what difference I saw in prop loop section (it changed the numbuffers from 4 to 2 and min/max distances so I changed tehm back to what my previous soundlist had). Still no avail. Still sounds like a p51 or similar which is not in my sounds list.

Yes. They sound normal when played in media player. Just ingame it doesn't sound right.

Hello all, First off thanks to all the moderators, modders etc who have put this site together! Bought WOV a long time ago got bored with it, moved on. Just happened to be on wikipedia (back in 08) looking up WOV when I found out about mods to the game and brought me here. Downloads all the good stuff, planes, maps, weapon packs etc. Played hard. Fast foreward to a week ago. My computer died on me with the HD unrecoverable (so far going to try unbuntu and linux to recover). Oh well time for newer better one right? :) Anyway sprang for a Alienware Aurora (windows 7 64) yada yada. Reinstalled WOV. Updated to 08 level. Installed the gold pack update/expansion weapons packs planes etc. Well so far everything works fine (learned alot through trial n error what not to do on first comp) except one wierd glitch that I haven't found anything about using search. My controls are all whacked. Using a saitek ST290 pro. Downloaded and installed their latest drivers for my system. All functions worked properly. Set up my key functions in options for my controls. No matter what I set or change for some reason anytime I use selected weapon (no matter if it's set to joystick/keys or mouse) it deploys airbrakes, Flare key/buttondrops chaffs, Chaff button does a mini freeze and all sorts of problems like that. Worked fine on stock install and problems are on all planes, all mission/campaign types etc. This is one part of the modding process I haven't seen read so I haven't a clue what to look into. The only problem I encountered in the modding so far is that part 1 of the 3 part gold pack will not unpack so it is not installed, but it worked fine directly after the install so I just started adding more. All my downloads are backed up so I can just wipeout and reinstall but I'd rather try to find out what to tweak if possible. My experience I would say is right at intermediate. I can do all the ini editing, adding weapons, familiar with the editors etc. so I'm not a total newb if that makes it any easier to try to figure out/help. Thanks in advance

@$%@. Yep was there. Don't know if that was the problem as I wiped it all out and started over 30 mins before you posted that :(. Oh well thanks now I'll know for future reference though. Going to build it a little slower this time though not install all the mods before playing after each