jrdani

First of all, I'd like to thank all the modders and skinners for making SFP1 and WOV the greatest sims ever as for as I'm concerned. Without your talent and generosity, they would be getting old and not nearly as interesting. Through your efforts, they remain young and alive. Its so much fun, even for an old retired guy like me, to install a new skin or mod, and takeoff knowing that there are new sights, sounds or effects to enjoy. Thank you all again..........now to my plea for help: I'm not new to installing skins or editing files (Decals.ini, etc.), but lately I'm having nothing but problems having F4J skins appear correctly in WOV (my primary sim). A year ago before my illness, I'd installed a dozen or so F4B and F4J skins in WOV with no problems whatsoever, which makes me wonder whether the latest patches (2 & 3) are causing my problems. The primary problem is decals not appearing at all (sometimes partially), usually on the vertical stabilizer, but sometimes as in the case of Allo's USNVF114 Aardvark, the fuselage stripe(s) doesn't appear either. I'm very careful to make sure that all files are in the proper folders and that the TextureSetXXX is in the plane's .ini file and numbered sequentially. I've worked for 24 hours or so now and tried everything I know with no success. As I always do, before posting a request for help, I've searched every website's forum. In particular, I've looked at every post in this Skinning Forum I thought might be applicable, all to no avail. The last thing I've tried is installing Allo's Aardvark mentioned above in my SFP1 sim, and voila, the stripes, the aardvarks, and everything appears. This must mean that some skins work in SFP1 and not in WOV.........can we know which skins work in which sims without experiencing the "agony of defeat"? Is there anything we can do to make them work in WOV? Please help, I'm worn out from fighting the problem. I look forward to your replies and thanks in advance for any assistance you can give me.

Thanks for the reply.............I'll look at the decals.ini files.

I've installed several new skins for the USMC F4B in SFP1's stock Desert Campaign. After selecting a new squadron in the "Loadout" screen, the stock (default is USMC Grey 1) squadron's tail art and markings (VMFA531) are still showing as if the new squadron's VMFA*** had been painted on without removing the old squadron designation. What can I do to correct this? I've looked at everything I can think of with "no joy". I've got a feeling it has something to do with the Loadout Screen's "Squadron Drop-down Menu". The instructions that came with some of the skins said to choose "None" in this menu, however "None" doesn't appear in that menu for me. The only thing that can be selected is: "VMFA-531 Grey Ghosts". What can I change to enable "None" as a choice?

Thanks for the info, hopefully Thirdwire will come out soon with the patches.

Thanks for the reply, USAFMTL, I didn't know that was part of the bug. Are the bugs pretty much resolved in SFP1 now, or is this WoV campaign bug, etc. existing in SFP1 as well?

I'm wondering if anyone else has experienced a similar CTD problem to the one I'm currently having in WoV as described below. When I attempt to re-enter and resume my ongoing Linebacker 1 campaign, it CTDs right after clicking the "Accept" button at the Campaign Loading Screen. This only started yesterday morning, after completion of some 15-20 missions in it. I have several other campaign files saved and in progress; ie Topgun, Vietnam Tomcats, etc. and LB1 is the only one crashing . I've tested by starting each of the others with no problems. I've checked to see what, if any, changes I made (or addons I added) might coincide with the problem's beginning. The only things were upgrading the Weapons Pack to the 20Mar05 issue, and adding some Tomcat skins (which shouldn't affect this campaign whatsoever). However, you'd think that if the Weapons Pack upgrade initiated the crashing of Linebacker 1, it would affect the other campaigns as well. Since I'd saved a week older version of this LB1.sav file in another place, I copied it to the PilotData folder, thereby overwriting the "corrupted" LB1.sav file. That seemed to correct the problem. I could then get back into the campaign and execute a mission, even though obviously I had to lose the missions I'd flown in the last week. But the cure was only temporary. I've found that after overwriting the corrupted file, I can execute several missions in succession without any problems. But when I exit WoV and then try to return another time and re-enter the LB1 campaign, it CTD's again, telling me this latest LB1.sav file has somehow become "corrupted" as well. Does anyone have any ideas? I've tried everything and looked everywhere on my own for an answer with "no joy". I look forward to, and thank you for, your responses.

Recently downloaded, installed Capun's beautiful AH-1W Supercobra, and took it on a test drive (the bombing range building mission). The only weapon I can get to fire is the gun. Could not get either the AGM119 or the rockets to fire from their pod. Could someone tell me what I'm doing wrong or not doing? Any light someone can shed on this for me will be much appreciated. My initial ineptitude aside, it's another fantastic job by Capun creating a flyable helo(s) in WoV/SFP1.

Sometime recently I downloaded the contents of a carrier practice mission which I believe was entitled, "F14_Deck_Quals". I have searched many search engines, using many different descriptions, and I have yet to find it again. For some reason, I seem to remember USAFMTL as the author, however I've looked on his web page with "no joy"......maybe my memory is slipping. Can someone please steer me in the right direction? Thanks in advance for your help.

Streakeagle, you are correct in deducing the problem is not enough data shown for the weapons you tried to select, along with many others you have shown in your WEAPONDATA.INI file. There are two ways I'd suggest you can correct this. The first: If you have a backup of your original WEAPONDATA.INI file, open it and for every "two-liner" weapon you showed above, cut and paste the missing data. Then resave the corrected WEAPONDATA.INI file, and you should then be "armed and dangerous". Make sure all of your weapons are sequentially numbered and that there is only one space between each before you "save". The second: Download the latest Weapons Pack revision, dated 1Mar05 (WeaponsPack_01Mar05.zip) from SimHQ.com, unzip it into a separate folder, find the included WEAPONDATA.INI file (after unzipping it will be in: \WeaponsPack_01Mar05\Weapons) folder and replace your "faulty" file with this one. It has almost every weapon we'll ever need to fly SFP1/WoV, including your Phoenix missiles which we need to fly the fantastic Tomcat campaign. Hope this helps you. You've been kind enough to help me on several occasions.

Look in your aircraft's *DATA.INI file, for example the following is from my F-4J's located for me in: \Wings Over Vietnam\Objects\Aircraft\F-4J: [sound] EngineSoundName=JetEngine AfterburnerSoundName=PhantomAfterburner DamagedEngineSoundName=PlaneFire FlapsSoundName=Flaps AirbrakesSoundName=Airbrakes GearsSoundName=Gear If the line: AfterburnerSoundName= is either blank or missing, then correct it using the desired sound's name shown in your sound folder, save the *DATA.INI file, and you should be good to go. If you don't see your aircraft's *DATA.INI file, then you'll have to extract it from the ObjectData.CAT file using the SFP1E Extraction utility which can be downloaded at: My Webpage This should solve your problem. Happy Flying!