Jump to content

jrdani

JUNIOR MEMBER
 View Profile  See their activity

  • Content count

    35

  • Joined

  • Last visited

Posts posted by jrdani

  1. Posted

    Can anyone tell me what file governs the "takeoff time" shown at the beginning of each campaign mission and subsequently shown on the Hangar screen? For example, in WOV the time is "teletyped" out right after the date on the Opening screen and then shown again on the Hangar screen. I used to think it was randomly generated, but I've now experienced a string of more than a dozen consecutive missions where it's exactly the same: 07:27:11. I've looked in what I thought were the most likely files for the "trigger", but so far I've struck out. If someone could point me in the right direction I'd appreciate it very much.

  2. Posted

    Thanks jrdani,

     

    Yes, I was matching the screen resolution (via the Cat control center settings) with the in-game resolution settings, and saw no solution to the cockpit image "tearing" (no tearing on the background environment though, don't know if that is significant...).

     

    I've tried HSync and VSync enabled and disabled, and all combinations... Nothing.

     

    What I did find out is that the monitor has no factory profile when attached through the DVI cable, however, I WAS able to color calibrate it when connected with the VGA port/cable that came with it (the monitor did not come with a DVI cable!). I suspect it is a firmware issue, and I have not heard back from the company.

     

    Good news, I'll take it back directly to Costco with no questions asked... Now I just have to go back to my 19" till I find a deal on a better brand! BUT I've gotten used to it for work, and that's going to be hard to take after all that realestate :boredom:

     

    B Bandy, if you're still shopping for a 22" widescreen, try looking at the 22" LCDs on TigerDirect.com. I've dealt with them numerous times during ths last several years and have always found them to be excellent to deal with, before and after the sale. I forgot to mention previously that I'm running my Optiquest Q22wb on a DVI cable that I purchased separately with good results achieved. You might also use Znet to compare prices around the web. Hope you have better luck with your next one.

  3. Posted

    You asked for input from anyone who installed a 22" widescreen monitor. I recently switched from a 17" CRT to a ViewSonic Optiquest 22" LCD with no problems whatsoever and the graphics are fantastic on the widescreen.

     

    You mentioned attempting to lower your PC's display resolution, but I didn't see any mention of whether or not you've changed the game(s)' graphics options to match your new monitor. I have my game's "Display Resolution" set to: 1680x1050x32 and the "Display Aspect Ratio" set to: Widescreen (16x10).

     

    You also mentioned changing all of the game's graphics settings to "Low" with no success. I think those settings are more dependent on the capabilities of your display adapter (video card) than your monitor. I have all of mine set to "High" with no problems. Make sure that your video card supports the resolution potential of your new monitor. It looks like yours should.

     

    Bottomline, your problem might be resolved by something as simple as making sure your game(s) display options (both resolution and aspect ratio) match your monitor and video card settings. I hope this information is helpful to you.

  5. Posted

    I've searched the archives for hours now, both here and at SimHQ, for ini editing info to enable the Ground Radar mode of Avionics70.dll to show a carrier's blip or an "updated/modified" Avionics70.dll file that would accomplish the same thing. I've been away from SFP1/WOV/WOE for over a year and I'm sure this problem was probably resolved at some time in the past. I just can't seem to find the record of it. I found a lot of info regarding Avionics70.dll in relation to CCIP display, etc., but nothing with respect to "blips" As you all know, it's very difficult to find the carrier, especially at night, without that blip. I also found statements indicating that A/G radar was not functional at that time in Avionics70.dll.

     

    I've recently installed the F/A18 Blue Angel model that was part of the C6 Megapack and everything works fine (A/A radar/TV Screen/CCIP, etc.) except the blip function of the A/G radar. If anyone could point me in the right direction I would be very grateful.

  9. Posted

    QUOTE(USAFMTL @ Jun 19 2006, 07:58 PM)

     

    Wait Wait Wait, Erik and Fates did all the work! I didnt do a thing to get it up but pace around. I just handle forum ops. Those 2 guys are the true heros.

     

    Congratulations to all of you and thank you for bringing back one of my favorite websites. I know you are all are proud of this site you've created and you have every right to be. Long live CombatAce. I'm sure you've made it such that the idiot that's been doing this can never do it again. I hope that he and others like him wind up behind bars which is where they deserve to be.

  10. Posted

    Thanks for your replies, Lexx and Capun.

     

    Lexx, I did get your comments and ideas at Thirdwire and I appreciate them. I'm trying some of your ideas at present. Thanks again for posting them.

     

    Capun, I did mod the [GraphicsSettings] in the FlightEngine.ini some time before having this problem. Also, I've checked and I do have the very latest DirectX 9.0c. I have an ATI 7500 All-In-Wonder graphics card. I'll try rolling back to the previous driver as you suggested to see if maybe that will solve it. I'll also check the Sound, Effects, etc. files as well.

     

    Thanks for taking the time to reply, guys. These things will give me several ways to try and resolve the issue.

  11. Posted

    I initially posted this in the General Discussion portion of this forum, but maybe I should have posted it here instead, so here goes: :help:

     

    Is there anything different that must be done in order to install older add-on aircraft in WOV, Patch 4a (5/25/06)? I've added the respective aircraft's folders of the E-2C, F-14A, FA-18A and F-16 to the ..........\Objects\Aircraft directory and modified the Options.ini file in the main Wings Over Vietnam folder to show an EndYear=2010 as suggested by USAFMTL.

     

    I've tested each one in the Single Mission scenario and the E-2C and F-16 work fine. However, I have one small problem with the FA-18A (not the latest one with the corrupted file) and the F-14A. If I simply load them and don't fly, I can hit the escape key to terminate the mission and they exit to the De-briefing Screen as they should. However, if I load them, fly around and then land, hitting the escape key won't exit to the De-briefing Screen. The screen stays black and I initially had to do a "hard" shutdown of the computer and then re-boot. I've waited as long as a hour to see if eventually the black screen would disappear. The computer is not "hung-up" because each time I can see and move my mouse pointer. I've recently found that if I hit the escape key a second time, it will return to the desktop but not to the Debriefing Screen where its supposed to be. :angry:

     

    The reason I'm asking if anything has to be different for WOV Patch 4a (5/25/06) is because I've copied the exact folders (FA-18a and F-14A) from WOV Patch 4a's Aircraft folder to WOV Patch 3's (7/5/05) Aircraft folder, tested them several times in Patch 3 and after flying and landing, hitting the escape key exits properly to the De-Brief Screen every time.

     

    As mentioned above, I have this problem only with the F-14A and the original FA-18A (not Blackbird's with the corrupted file) and only in WOV Patch 4a (5/25/06). Works fine in Patch 3. I've tried everything I can think of to fix it with no success. I've removed and re-installed both the F-14A and the FA-18A several times. I've defragged the hard drive. I've compared all of the ini's between the F-16 that works with the F-14A that doesn't, and nothing different jumps out at me. I've even copied the entire WOV Patch 4a folder to a 160 gig backup hard drive and tested it there with the exact same results. I've searched the forums of CombatAce, SimHQ and Column5, and if the answer's there, I must have missed it, but I've sure searched hard. :sad:

     

    Just today downloaded, installed and tested the F-15A Eagle in WOV Patch 4a. It exits to the Debriefing Screen just as it should. BTW, the F-15 is beautiful.........kudos to the Mirage Factory. :clapping:

     

    I hope some of you modders out there have some ideas? Any help would be much appreciated. :help:

  12. Posted

    Bump

     

    I have this problem (see original post) only with the F-14A and the FA-18A (not Blackbird's with the corrupted file) and only in WOV Patch 4a (5/25/06). Works fine in Patch 3. I've tried everything I can think of to fix it with no success. Doesn't anyone have any ideas? Any help would be much appreciated.

     

    Just downloaded, installed and tested the F-15A Eagle in WOV Patch 4a. It exits to the Debriefing Screen just as it should. BTW, the F-15 is beautiful.........kudos to the Mirage Factory.

  13. Posted

    Is there anything different that must be done in order to install add-on aircraft in WOV, Patch 4a (5/25/06)?

    I've added the respective aircraft's folder; ie. E-2C, F-14A, FA-18A, F-16 to the ..........\Objects\Aircraft directory and modified the Options.ini file in the main Wings Over Vietnam folder to show an EndYear=2010.

     

    I've tested each one in the Single Mission scenario and the E-2C and F-16 work fine. However, I have one small problem with the FA-18A (not the latest one with the corrupted file) and the F-14A. If I simply load them and don't fly, I can hit the escape key to terminate the mission and they exit to the De-briefing Screen as they should. However, if I load them, fly around and then land, hitting the escape key won't exit to the De-briefing Screen. The screen stays black and I have to do a "hard" shutdown of the computer and then re-boot. I've waited as long as a hour to see if eventually the black screen would disappear. The computer is not "hung-up" because each time I can see and move my mouse pointer.

     

    The reason I'm asking if anything has to be different for WOV Patch 4a (5/25/06) is because I've copied the exact folders (FA-18a and F-14A) from WOV Patch 4a's Aircraft folder to WOV Patch 3's (7/5/05) Aircraft folder, tested them several times in Patch 3 and after flying and landing, hitting the escape key exits properly to the De-Brief Screen every time.

     

    Thanks in advance for any guidance anyone can give me because at this point I'm clueless.

  14. Posted

    I downloaded it twice and it was corrupt. So I deleted it. Not sure howmany other people had issues either. I didnt get any reports though.

    I had a problem also as follows:

     

    Recently added the FA-18A Hornet to my fully patched WOV (5/25/06). Thus far, I've only tried single missions. After landing and completing the mission, I hit the escape key as usual to go to the de-briefing screen. However, the screen just remains totally black, and after waiting about 5 minutes, I have to shutdown the computer and reboot. While the screen is black, I can see the mouse pointer and even move it, but the game won't go to the de-briefing screen or return to the desktop. This has happened every time (3).

     

    I've done an exhaustive forum search and have found other black screen probs, but nothing similar to this one. Any ideas?

  15. Posted

    Hengist

    Member

    Member # 1336

     

    posted November 17, 2005 07:57

    --------------------------------------------------------------------------------

    Are there any mods out there for WoV, that enables a fleet rather than just the one solitary A/C carrier, for the campaign that comes with the game?

     

    --------------------

    Hengist.

    Hengist's MiG Alley Site

     

    --------------------------------------------------------------------------------

    Posts: 1489 | From: Balsa Munitions R&D Institution, England - Leaders in retrievable Torpedo tech | Registered: Aug 2000 | IP: Logged

     

    Gramps

    Member

    Member # 7688

     

    posted November 17, 2005 15:46

    --------------------------------------------------------------------------------

    Only my (currently unavailable) Aussie Carrier Mod fo WoV. It's easy enough to do (not hard, just time consuming), so anybody should be able to duplicate what I've done and just change the objects to whatever you want. Having said that, I made it a long time ago and haven't tested it with the latest patch. Things may have changed, I don't know.

     

    Could someone whose added other moving ships in formation (cruisers, DE's, tanker, etc.)to a WOV/SFP1 campaign carrier, therefore creating a carrier group, steer me in the right direction as to the "how to"? I've searched and searched the posting archives and the above quoted post from Hengist with Gramps' reply is the closest thing to info I've found, however I'm not able to find Gramps' Aussie carrier mod to compare ini entries. Any help and/or information would be greatly appreciated.

  16. Posted

    quote:

    --------------------------------------------------------------------------------

    Originally posted by RogueSnake:

    Ok, remember, Uber noobie here

     

    Is there a way to make this carrier replace one in one of the default campaigns? I tried deleting the Kitty Hawk.

     

    a. If Already Extracted, Remove Previous CVN_Carrier Entry

     

    And my plane just explodes on mission start.

     

    Or should I just search for missions/campaigns that use it? Thx for the help

    --------------------------------------------------------------------------------

     

    You can Replace the Carrier in the Campaigns by opening the Campaign_Data.ini (has to be extracted of course)

     

    and Go down to Carrier Units, and Change the Following lines that Are Bold

     

    [CarrierUnitXXX]

    CarrierType=CVN75

    CarrierNumber=75

    UnitName=CVN-75 Truman

     

    --------------------

    Digital Overload

     

    I've tried the above with no success. I've searched all the forums looking for more info to no avail, so I'm turning to the pros and/or anyone who has done this successfully for help.

     

    I know I've installed DO's beautiful CVN75 correctly because I can get it to work fine in "single missions", however, I've tried everything I know of to get it to appear in the WOV LB1 Campaign and have struck out so far. I've removed all other mentions of carrier units in the WOVCAMPL1_DATA.INI file and put in only the following reference:

     

    [CarrierUnit001]

    CarrierType=CVN75

    CarrierNumber=75

    UnitName=CVN-75 Truman

    ForceID=1

    Nation=USN

    ;StartDate=6/1972

    StartDate=5/1964

    BaseArea=Yankee Station

    NumSquadron=5

    BaseSize=MEDIUM

    Experience=100

    Morale=100

    Supply=100

     

    Now when I try to start a mission in this campaign, instead of the flight being on the cats, ready to takeoff, it's on the surface of the water. I know I'm missing something or doing something wrong, but I can't figure out what it is.

     

    Thanks in advance for any assistance anyone can give me.

  19. Posted

    :help: Can anyone tell me where to locate these files: [2284]Updated_Vietnamsea_AF_4_Light_Pack.rar,

    [2183]18_and_36_lights_for_SF_WOV_with_the_runway_upgrades.rar, and [2209]Helopad_Lights_Airfield_2.rar, all by Eightlein? I downloaded these files from CombatAce about 4-5 weeks ago and need to download them again, but can't find them anywhere. I've also done an extensive search in the file download area and can't find them there either. Is there an archive someplace where files are moved to after being posted in the download area for a few weeks?

  20. Posted

    Thanks for your comments USAFMTL, JSF Aggie and Capun. I'm incorporating all of them and worked on this all last night. USAFMTL, I did a search on FlightEngine.ini and based on some of the edits I read about, I changed my GraphicsSettings and HighDetailOption to read as follows:

     

    [GraphicsSettings]

    ZBufferDepth=24

    MaxVertexCount=16384

    MaxIndexCount=32768

    MaxTextureCount=16384

    MaxModelType=2048

    MaxMeshPerScene=2048

    MaxModelPerScene=4096

    MaxLightPerScene=1024

    AspectRatio=1.333333

    MinPixelSize=1.0

     

    [HighDetailOption]

    ;HorizonDistance=75000.0 (4/22/06 jrd)

    HorizonDistance=85000.0

    DetailMeshSize=6

    DetailLevel=1

    WaterEffect=1

    NoiseTexture=1

    ;MaxTextureRes=0 (4/22/06 jrd)

    MaxTextureRes=512

     

    USAFMTL, is this the flightengine.ini tweak you referred to? I made the HorizonDistance and MaxTextureRes changes based on something Fubar512 had posted on October 19, 2005. I had previously changed the MaxTextureRes from -1 to 0 based on Charles' SF Editing Notes. Which is the correct MaxTextureRes value?

     

    I'm currently re-installing each skin in my WOV Patch3, and looking at each one, using the above edits to the FlightEngine.ini file. Thanks again for everyone's comments and I'll keep watching this thread for anything else you might think of. I'll also post the results.

  21. Posted

    Thanks to all of you who create and share the fantastic skins that we all enjoy so much. Your abilities and talents are truly amazing. I wanted to give you an update on a previous post I'd made regarding skins, decals, etc. I've been trying to use these skins on the F-4J in WOV's Linebacker I campaign (listed as filenames): tomcatters_2.7z, atfusnvf33f-4j.zip, fighting_falcons_2.7z, VF101.7z, atfusnvf102f-4j.zip, VF114.7z, vigilantes_2.7z, chargers_2.7z, lancers_2.7z, death_angels_2.7z, shamrocks_2.7z and [982]F_4j_VMFA_451.rar.

     

    Your replies to my previous post eventually led me to some very interesting discoveries by trial and error testing. Because I'd had no problems with any of the skins I was using a year ago in WOV-Patch 1, I created a clean (stock-no mods) install of WOV, added patches one at a time through patch 3 and re-installed skins one at a time, testing in both Single Mission and Campaign after each skin installation. None of them worked completely in either Single Mission or Campaign using Patch 3. Numbers and/or markings were missing on virtually every skin. I even tried changing graphic options, particularly "Object Texture" to medium and then low with still no complete success, and as you know, when lowering this option some markings that do show appear blurred or almost erased. I don't think my computer is a limiting factor as I have a 1.7 gig processor with 1024 meg ram, a 160 meg HD and an ATI All-In-Wonder 8500 video card.

     

    As I stated above, I knew they had worked after patch 1, so I created another "clean" stock install, patched it through Patch 2 and re-installed the skins, again testing in Single Mission and Campaign mode after each skin installation. Every skin worked in Single Mission and Campaign, using Patch 2 (I had all graphics options set on "high" with mirrors and reflections "off"). I then re-installed the mods I'd been using previously (enhanced VietnamSea tiles, enhanced water, sky mods, etc.) and tested the skins again. All skins continue to work completely using Patch 2 with all graphics settings on "High".

     

    Given the above results, the only conclusion I could draw from this is that maybe something in Patch 3 changed the way object textures are handled (handled may not be the correct term). I've re-read the Readme issued with Patch 3 trying to re-review what was changed and looking for some clue as to what to do on my own to correct this problem. I've tried everything I can think of, but I cannot correct it. Given the above information, do any of you have any ideas? Is there anything I can do to enable these skins to function normally in Patch 3? If not, is this something that could maybe be addressed in Thirdwire's next patch or maybe on future skins? I would enjoy using these beautiful skins in Patch 3 if at all possible.

     

    Finally, I'd like to take this opportunity to again thank each and every one of you for creating these skins that add so much beauty and realism to our sims, bringing so much enjoyment to all of us. Thank you also for your previous help and for always being so generous with your time and knowledge. Please give me any and all comments, ideas, opinions, etc. regarding this issue.

  22. Posted

    Thanks again everyone for your replies to my previous post regarding this issue. I wasn't able to get online all day yesterday because of more health issues, but I'm feeling better now and last night was able to try some additional things regarding this missing decal(s) issue. The results of this experiment left me with more skinning questions as I'll try to explain below.

     

    As I mentioned earlier in the other thread, a couple of days ago I installed nine skins on the F-4J in SFP1 [6 or 7 of which I'd attempted previously in WOV with missing decal(s) results]. Every decal on every skin appeared perfectly in SFP1.

     

    Since then, I've tried to implement everyone's suggestions (responding to my plea for help) in WOV with no success. After Dave (USAFMTL) posted that Allo's Aardvark skin worked in his copy of WOV and that I might have to "do the dreaded uninstall and reinstall", I decided to try that as well (BTW Dave, my oldest grandson's completing his freshman year at the AFA. He loves it, made the Dean's List last semester, and hopes to be a fighter pilot. He's also a quarterback on the football team and had a great freshman season).

     

    Last night I took a "clean install" and fully patched copy of WOV and installed and tested each problematic skin, one at a time, beginning with the VF114 Aardvark, and continuing with VF31 Tomcatters, VF33 Tarsiers and VF96 Fighting Falcons. Each skin produced the same result (missing decals) as it had in my fully modded version of WOV. Missing decals were: (VF31) Red stripe, squadron no. and USS Saratoga on both sides of the fuselage; (VF33) Gold star w/AG, lightning bolt and plane no., all on both sides of the vertical stabilizer; (VF96) Black falcon and plane no. on both sides of the vertical stabilizer; (VF114) Slanted stripe(s) on the fuselage and aardvarks on the vertical stabilizer.

     

    Because of these results, I stopped installing skins and decided to try some "trial and error" with respect to graphic settings in the Options Menu. My usual configuration has everything set to "High" with horizon "Normal" and cockpit mirrors, cockpit reflection and shadow "Off". I changed the settings one at a time and tested each change. When (and only when) I set the Object Texture to "Medium", every missing decal appeared on every skin except the VF114 Aardvark's fuselage striping and the little aardvarks on the v/s. However, when using this "Medium" setting, many smaller details seriously bleed, fade and blur, such as squadron nos., plane numbers, ship ID, etc. So this tradeoff of component appearance versus component visibility doesn't seem to be a viable solution.

     

    As mentioned above, I'm now left with more questions regarding skins and sim differences which I'm sure my lack of experience and knowledge contributes to. Some of these questions are: (1) Why do all of these skins show perfectly in SFP1 with all graphics settings on "High" and even cockpit mirrors, cockpit reflection and shadow "On", but not in a clean and patched WOV installation using less demanding graphics settings? (2) Does this mean there are fundamental differences in the architecture of SFP1 and WOV? (3) Are there fundamental differences in the architecture and composition of different skins regarding their ability to "stick"? (4) Every one of my ten F-4B skins I'd installed previously in WOV show perfectly. Does this mean there's that much difference between different versions of the same plane regarding skins of similar complexity and detail?

     

    I'd like to thank everyone again for their advice and suggestions. The reason for my initial post was to get help in resolving an issue and to gain more experience by learning more about that issue from all of you. The reason for this post is to pass on what I've learned from my recent trial and error testing in the hope that it might help some newer "newbie" than myself, and hopefully, to get some answers and/or opinions with respect to the questions listed above.

     

    In closing, I'd also like to say to all the "skinners" that the detail and beauty of your creations make flying these two sims a much more enjoyable and visually pleasing experience for me, and I'm sure, everyone else as well. Thanks so much for your efforts.

  24. Posted

    Dave, in response to your question, some tga's do and some don't. I'd found your previous post re: the placement of tga files ending in 000 during one of my searches a couple of days ago. I followed your instructions, but it didn't seem to make any difference in my case.

     

    I've also read and re-read TK's Decal tutorial and I'm going to read it again when I'm not so tired. However, I haven't seen anything that jumps out at me regarding a solution to this problem.

     

    Here's some interesting information based on a little test I just completed. Every F4J skin I installed tonight in SFP1 worked with no problem whatsoever, just by following the usual instructions: "Put each TextureSet in numerical order in the F-4J.ini file and copy the skin's folder to the F-4J folder". The skins were: USNVF31, ATFUSNVF33, USNVF96, VF101, VF114, USNVF151, VMFA212, VMFA235 and VMFA333. I took a close look at each one and every decal and marking shows perfectly. Conversely, I've tried at least 6 or 7 of these same skins in WOV with 1 or more decals missing or partially missing. If anyone needs specifics on any of these, I'll be glad to furnish them.

     

    I don't remember ever seeing a caution that certain skins were only for SF and would not work on the same plane in WOV. As I mentioned in my initial post, because I didn't have SFP1 yet, I'd installed probably 12-15 skins in WOV about a year ago with no problem at all so this recent development was a surprise. I appreciate the help from all of you and I know that you experienced fellas can resolve this issue or maybe know someone who already has. I didn't think there was that much difference between the two sims, architecturally speaking, but if there is, maybe there's a conversion procedure that might correct the skin incompatability. Thanks again for taking the time to help.

  25. Posted

    Thanks for the reply, Dave. The link to the skin is as follows: Allo's F-4J USNVF114 Aardvark

     

    The Decals.ini is as follows:

     

    [Decal001]

    MeshName=fuselage_P

    DecalLevel=0

    DecalFacing=RIGHT

    FilenameFormat=Insignia

    Position=4.63,-0.167

    Rotation=0.0

    Scale=1.85

    DecalMaxLOD=4

     

    [Decal002]

    MeshName=fuselage_P

    DecalLevel=0

    DecalFacing=LEFT

    FilenameFormat=Insignia

    Position=4.63,-0.167

    Rotation=0.0

    Scale=1.85

    DecalMaxLOD=4

     

    [Decal003]

    MeshName=wing_left_outer

    DecalLevel=0

    DecalFacing=TOP

    FilenameFormat=Insignia

    Position=-4.241,-0.94

    Rotation=40.0

    Scale=2.5

    DecalMaxLOD=4

     

    [Decal004]

    MeshName=wing_right_outer

    DecalLevel=0

    DecalFacing=BOTTOM

    FilenameFormat=Insignia

    Position=4.241,-0.94

    Rotation=40.0

    Scale=2.5

    DecalMaxLOD=4

     

    [Decal005]

    MeshName=wing_left_inner

    DecalLevel=0

    DecalFacing=TOP

    FilenameFormat=Insignia

    Position=-4.241,-0.94

    Rotation=40.0

    Scale=2.5

    DecalMaxLOD=3

     

    [Decal006]

    MeshName=wing_right_inner

    DecalLevel=0

    DecalFacing=BOTTOM

    FilenameFormat=Insignia

    Position=4.241,-0.94

    Rotation=40.0

    Scale=2.5

    DecalMaxLOD=3

     

    [Decal007]

    MeshName=fuselage_front

    DecalLevel=2

    DecalFacing=RIGHT

    FilenameFormat=USNFighterNum

    Position=8.138,-0.418

    Rotation=0.0

    Scale=0.55

    DecalMaxLOD=3

     

    [Decal008]

    MeshName=fuselage_front

    DecalLevel=2

    DecalFacing=LEFT

    FilenameFormat=USNFighterNum

    Position=8.138,-0.418

    Rotation=0.0

    Scale=0.55

    DecalMaxLOD=3

     

    [Decal009]

    MeshName=vertical_stabilizer

    DecalLevel=0

    DecalFacing=LEFT

    FilenameFormat=F-4J/VF114/D/Aardvark

    Position=-4.40,1.50

    Rotation=0.0

    Scale=1.35

    DecalMaxLOD=4

     

    [Decal010]

    MeshName=vertical_stabilizer

    DecalLevel=0

    DecalFacing=RIGHT

    FilenameFormat=F-4J/VF114/D/Aardvark

    Position=-4.40,1.50

    Rotation=0.0

    Scale=1.35

    DecalMaxLOD=4

    Reverse=TRUE

     

    [Decal011]

    MeshName=fuselage_P

    DecalLevel=0

    DecalFacing=RIGHT

    FilenameFormat=F-4J/VF114/D/Str

    Position=0.550,0.200

    Rotation=-65.0

    Scale=6.5

    DecalMaxLOD=3

     

    [Decal012]

    MeshName=fuselage_P

    DecalLevel=0

    DecalFacing=LEFT

    FilenameFormat=F-4J/VF114/D/Str

    Position=0.550,0.200

    Rotation=-65.0

    Scale=6.5

    DecalMaxLOD=3

    Reverse=TRUE

     

    [Decal013]

    MeshName=fuselage_P

    DecalLevel=0

    DecalFacing=LEFT

    FilenameFormat=NationName

    Position=-1.450,-0.335

    Rotation=0.0

    Scale=2.2

    DecalMaxLOD=3

     

    [Decal014]

    MeshName=fuselage_P

    DecalLevel=0

    DecalFacing=RIGHT

    FilenameFormat=NationName

    Position=-1.450,-0.335

    Rotation=0.0

    Scale=2.2

    DecalMaxLOD=3

     

    [Decal015]

    MeshName=vertical_stabilizer

    DecalLevel=1

    DecalFacing=RIGHT

    FilenameFormat=F-4J/VF114/D/NH

    Position=-5.80,1.8

    Rotation=0.0

    Scale=1.65

    DecalMaxLOD=3

     

    [Decal016]

    MeshName=vertical_stabilizer

    DecalLevel=1

    DecalFacing=LEFT

    FilenameFormat=F-4J/VF114/D/NH

    Position=-5.80,1.8

    Rotation=0.0

    Scale=1.65

    DecalMaxLOD=3

     

    [Decal017]

    MeshName=wing_right_outer

    DecalLevel=0

    DecalFacing=TOP

    FilenameFormat=F-4J/VF114/D/NH

    Position=4.800,-1.60

    Rotation=-20.0

    Scale=1.5

    DecalMaxLOD=4

     

    [Decal018]

    MeshName=wing_left_outer

    DecalLevel=0

    DecalFacing=BOTTOM

    FilenameFormat=F-4J/VF114/D/NH

    Position=-4.800,-1.60

    Rotation=-20.0

    Scale=1.5

    DecalMaxLOD=4

     

    [Decal019]

    MeshName=rudder

    DecalLevel=2

    DecalFacing=RIGHT

    FilenameFormat=USNFighterNum

    Position=-7.10,2.00

    Rotation=0.0

    Scale=0.50

    DecalMaxLOD=4

     

    [Decal020]

    MeshName=rudder

    DecalLevel=2

    DecalFacing=LEFT

    FilenameFormat=USNFighterNum

    Position=-7.10,2.00

    Rotation=0.0

    Scale=0.50

    DecalMaxLOD=4

     

    [Decal021]

    MeshName=flap_inner_right

    DecalLevel=2

    DecalFacing=TOP

    FilenameFormat=USNFighterNum

    Position=2.2,-1.78

    Rotation=-14.0

    Scale=0.75

    DecalMaxLOD=4

     

    [Decal022]

    MeshName=flap_inner_left

    DecalLevel=2

    DecalFacing=TOP

    FilenameFormat=USNFighterNum

    Position=-2.2,-1.78

    Rotation=14.0

    Scale=0.75

    DecalMaxLOD=4

     

    Again, thanks for looking at this. I've had similar problems with other F-4J skins as well and I hope you can steer me in the right direction.

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..

  I accept