Jump to content

JSF_Aggie

+MODDER
  • Content count

    975
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by JSF_Aggie

  1. The variable is at the top of the campaign's _data.ini file. It's something like WeaponSupplyTime, and the value is in days. You must be playing the Harrier Campaign with Campaign Length set to long. My intent was to set the Supplytime so far out in the future that you would never get resupplied. The MaxMissions is set to 30, but I think this is scewed by the Campaign Length option.
  2. Very cool. If you do any more, please post them.
  3. My dad's computer is as follows: 3.2 P4 1 Gig Ram Nvidia 7600 GS AGP He recently had some local computer shop reinstall XP for him because it wasn't booting. I sat down today to reinstall his WOE and some other games. Updated to the latest version of DirectX & loaded the 163.75 Forceware drivers. I also grabbed any critical XP updates. My graphical framerates suck. Stock WOE install, sitting on the runway, cockpit view of the F-15, I'm getting about 8 fps for Graphics, and 53 Game. If I go the external view of the aircraft and shoot the gun, I drop down to 4 fps for my graphics. I use to average about 20, if not 30, on his machine. AA, anisotropic filtering, & v-sync are off. I'm running at 1280x1024, but going down to 1024x768 gives no graphical improvement at all. I've checked everything I can think of in the Nvidia control panel and the bios. Does anyone have any suggestions of things I can check? Thanks.
  4. Need Help Diagnosing A Graphics Problem

    IL-2 running as an Open-GL app runs fine. I did try reinstalling DirectX and the Nvidia drivers with no luck. I bit the bullet and re-formated the harddrive. I'm half-way through reinstalling & updating everything, so we'll see. Thanks
  5. Need Help Diagnosing A Graphics Problem

    Thanks for the reply. Both of those are good, so I'm still looking around.
  6. Rant on

    Agreed. It'll die down for awhile now, but it will always come back again. Just ignore it, and do what makes you happy. Don't let it take away from your own enjoyment.
  7. Very nice AC, skins, and flight model. Thanks.
  8. From a guy I work with who flew the G in Desert Storm: "Yes, you could carry four AIM-7s in the fuselage recessed stations. You are right, we usually carried an ECM pod in the forward left station (WW carried the ALQ-184). No restrictions that I can recall on AIM-7 employment due to carriage of the high-speed centerline tank (600 gal)."
  9. Did you get the patch from Thirdwire? After it's patched, it doesn't ask for the CD.
  10. I first got the game about 3 months before patch2 showed up, so I missed most of the "fun" on the simhq forum. No other sim has all the aircraft I watched and read about growing up. Big thanks to Deuces who got me going with Photoshop.
  11. This is a fictional campaign I'm working on for Strike Fighters. It's set in 1978, on a heavily modified version of the stock SFP1 desert terrain. It will be Paran vs. Dhimar, with help from the US Navy and Marines. Dhimar's air force will consist of F-4D's, F-5E's, and A-4F's. The USMC will be the VMFA-542 Tigers, split up among 3 different forward operations bases. One of which is pictured below. The USN will be represented by the USS Nimitz, and the squadrons that sailed with her on her '78 cruise: VF-84 Jolly Rogers - F-14A VF-41 Black Aces - F-14A VA-82 Marauders - A-7E VA-86 Sidewinders - A-7E VA-35 Black Panthers - A-6E With the exception of the AV-8C, and the F-14, the skins below are done new for this campaign.
  12. Can't wait to dust some crops.
  13. Allen, I think I made the .tga textures for the forward ops bases and the two Dhimari airfields to large for your system to handle. A good test would be to fly the campaign as a F-4. The harrier bases are made from one large texture, where as the F-4 base was made from about 10. You'll probably just need to resize the textures to something smaller. In the terrain dir, look for all the runway7 - runway11 .tga's and resize them to something smaller.
  14. patch and expansion 1

    You do not need to patch a clean install prior to installing the expansion.
  15. RAF F-35 Helmet...

    It's much lighter than it looks. I've worn the prototype and it didn't feel awkward or uncomfortable at all. I expected it to feel top heavy, but it did not. It's the only helmet I've worn, so I can't compare it to anything current.
  16. RAF F-35 Helmet...

    The F-35 has a HMD (helmet mounted display), instead of a HUD. That's were the green lights are coming from. Ugly yes, but far from a POS.
  17. Boo Boo of The Day

    I'll sleep better tonight just knowing I'm being protected by TSgt Slavens.
  18. Yes, just install them AFTER the Harrier Campaign executable. Otherwise they will be overwritten by Deuces's effects when you run the exe.
  19. It must be patched to v08-30-2006, or you'll have no chance of it working. Read throught the README again to be safe. It tells you exactly what to do to install it.
  20. There are three potentials for conflicts: - My changes to the terrain will brake the default SFP1 campaign, because airbases were removed from the stock desert terrain. - I included a modified Nations.ini that has Dhimar and Paran added. If you've done something with yours, the changes will be overwritten. No changes to the squadronlist.ini were made - This installs the weapons pack. However, it does not include the modified _data.ini's for the stock aircraft that normally come in the pack. If you haven't already installed the weapons pack, you could have issues with both stock and 3rd party aircraft not having any weapons. This is because of how the AttachmentType is defined in each aircraft's _data.ini, for each station. There's much more in the knowledge base about this if you're not already familar. If you can work around those, you're fine dropping it into your current install. My request that a seperate install be used is primarly to keep me from trying to track down someone's problem, when I have no idea what they have in their install.
  21. The problem with that is the people that are pissing people off wouldn't read it anyways. F-22 stickie come to mind?
  22. Glad you got it working. I still can't duplicate it however. I ran the installer on a temp directory, and it did place the CVN68 inside the GroundObject folder, not the Objects folder.
  23. Akwar, Do you mean CVN68? That is the carrier used in this campaign. I can't duplicate your problem with any of the naval squadrons. Have you done anything to your Strike Fighters install besides install the Harrier Campaign executable? Are you sure you're patched to the latest? Does it say v08.30.07 in the bottom right corner of your mainscreen? You can always run the executable again on the existing install. Can anyone else confirm the issue, or confirm that it works? I play this campaign as a Tomcat as much as I do a Harrier.
  24. crl848, The only way to prevent that is to remove all the other stock aircraft, not used in the campaign, from your Aircraft folder. There's a variable in the campaign.dll to specify the FAC aircraft, but the game doesn't listen. It will randomly pick any aircraft that has FAC defined in it's capability list. You could also edit out FAC from all their _data.ini's. I have them all removed, and I get one of 3 FAC aircraft: USMC Bronco, Dhimar A-4E, Dhimar F-4D, all with proper skins. I suggest just going out in 2-ships. Without editing the campaign_data.ini, you only have 8 pilots and 6 AV-8C's to make it through 30 missions. There is a bug in the game that allows you to put an aircraft in the air for every pilot you have, even if you don't have that many aircraft. Kreelin, I agree that's it's more difficult to bring into a hover and land. Also, at 12k feet, I sent my wingman after a MiG. Within a few moments he got himself into a slow, flat spin, with about 10 deg nose down. I watched him not recover all the way down to the ground.
×

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