Jump to content

alexis99

VALUED MEMBER
  • Content count

    461
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by alexis99

  1. Has anybody dared to update to the new Win 10 yet, and if so, does it screw SF2 up?
  2. Thank you, gentlemen, I can leave my safe space now. Wrench: If you aren't on Win 10, you may have misunderstood my point. Every time I switch on, Microsoft is insisting I download the latest massive update. It's like they are issuing a Windows 11, not a little fix. Massive changes worry me. The reason I have migrated to SF2 is that I was on XP with SF1 and my XP graphics card went AWOL. SF2 is designed for Win7, the fact that it works on Win 10 is nothing short of a miracle. I'm in constant fear of it not doing any more. It wouldn't be the first time that Bill Gates has torpedoed my favourite flight sim by upgrading.
  3. Well, if you need me again, just whistle.
  4. Gosh, spanking the donkey has a different connotation in the UK. My dad says I've just received the equivalent of Sam Spade being hit over the head with a chair, thrown outside and been told "Stay off the case." Moose Malloy came up in conversation.
  5. Head bob. I thought that referred to the way the cockpit vibrates up and down when you reach certain speeds. I find that annoying. The vibration is nearly always there in small or large amounts. The cockpit moves up and down on the scenery view. The problem is that when it does this, those beautiful fine details in the cockpit start to flash. So where there are single lines, like in the Attitude Indicator, they move up to where the next line is, and then back down again, rapidly. The result is that you get jiggling lines are unpleasant to look at. It's worse when the contrast between the line and the background is high. Like in the Attitude Indicator. It's particularly bad in a cockpit like the EF 2000 Typhoon, which is a beautifully detailed piece of art. Unfortunately, the head bob causes those fine lines and superimposed button discretes to jiggle annoyingly. I'm at unlimited cockpit on a 27" screen, and it's like the whole cockpit is flashing. All planes do this to different degrees. The closer you zoom in, the less it happens, but you have to zoom in to a ridiculous degree. Now I've mentioned this, you'll not be able to avoid seeing it, so my apologies. But if we want to enjoy fine detail in cockpits, we need cockpits that are locked to the background image. So how can that be done. If we crowdfund TK for his next opus, can we persuade him to tell us how to stop the cockpit moving?
  6. So, merging. What's the protocol? What's the SP? What's the word on the street? Hypothetical set-up: You have SF2 and SF2NA. So now you can fly the F-100 Super Sabre in either version. Because all your scenery and all your aircraft can be accessed from either SF2 or SF2NA. So which version do you choose to fly in? Is there any issue that would make a player choose one over the other? The question arises, because if hypothetically I mod the Super Sabre in "user/etc/etc/ SF2/etc" with some furry dice in the cockpit window, then that mod only shows up in SF2; it does not show up in SF2NA. So presumably, you would have to put every mod in every version of the game you have merged. Unless of course, the insider info from you vets suggests otherwise. Grazie
  7. Thanks too, Wrench, you just popped in as I was thanking Eric. I can see the advantage of dumping specific aircraft from Israel or Vietnam. I go for SF2NA on account of the carriers in single missions. So I can fly your Libya and Desert 4 from carriers. That's good enough for me to stay that course. Okay, I'm good to go.
  8. Thanks, Eric, I was hoping this would be the answer.
  9. Think I'll be fine now. Thanks
  10. And decals??? Just noticed that. They're in the wrong place too.
  11. Okay, great, well-spotted. Thank you. In SF2 Pilot folder goes in Objects folder. Right. I'll fix that. The only things I have in Objects folder are Aircraft, Ground Objects, Weapons, Guns. Now I add Pilots. Does anything else go in there?
  12. The EF-2000_RAF was an interesting one. I am only flying the RAF version, I dropped the others to save space. In the crew section of the EF-2000_RAF_DATA it had [Pilot] SystemType=PILOT_COCKPIT PilotModelName=EF2000Pilot2 etc and also [Pirate_RAF] SystemType=PILOT_COCKPIT PilotModelName=fakepilot etc Under these conditions, I had a second pilot's legs hanging underneath the fuselage, which the centre tank covered when installed. By removing the [Pirate_RAF] entry in the above mentioned DATA file, I got rid of the hanging legs. So all is well. I have spent countless hours in the SF1 series, usually flying Intruders in Vietnam. I have also flown the Harrier and EF2000. I have never seen double pilot's before. Although in the EF-2000, you had to make sure the Typhoon pilot files were in the right place, otherwise his legs were hanging outside, below the pilot seat (i.e the default pilot sat too low). I have only just got SF2 and I am being careful to ask on here if I feel I have done something wrong, because it is a little different to SF1. However, there is a lot of similarity, so my experience has allowed me to fix most issues. The only one going unanswered is the issue of the black tanks that are permanently on the A-6E_TRAM. I fixed that by not flying the A-6E_TRAM
  13. Data folder is AV-8B-Plus_DATA. I was using shorthand. My apologies if I confused you. The pilot that is in the cockpit is SystemName[001]=Pilot-seat. [Pilot-seat] SystemType=PILOT_COCKPIT PilotModelName=Pilot_USMC etc The pilot that is not in the cockpit any more is SystemName[015]=pilot. [pilot] PilotModelName= ParentComponentName=Nose DetachWhenDestroyed=TRUE SystemType=GUNNER_STATION TargetType=AIR_AND_GROUND SeatID=4 GunnerID=2 PitchModelNodeName=headpitch YawModelNodeName=head GunRange=6500 PitchAngleRate=90 MaxPitch=20 MinPitch=-10 DefaultPitchAngle=-5.0 YawLimited=TRUE YawAngleRate=80 MaxYaw=70 MinYaw=-70 DefaultYawAngle=0 He's gone. I also removed this stuff: ****Manual parking animation**** /[Parking] /SystemType=ANIMATION /InputName=ANIMATION_2 /DeploymentMethod=MANUAL /AnimationTime=0.5 /AnimationID=2 **** Automatic on board/flightline animation **** [Parking] SystemType=PILOT_COCKPIT PilotModelName=FakePilot SeatID= Position=-0.0,4.0,0.83 CanopyNodeName= CanopyAnimationID=2 I removed it because it was another pilot entry and I figured it best to just have one pilot. My fake pilot mod folder is just fine. It's only got three entries, and it's in users\ etc etc \StrikeFighters2 North Atlantic\Pilots Anyway, the point is that I removed the second pilot from the aircraft by deleting the word "pilot" from SystemName[015]=pilot.
  14. Yes, I do. I had to do some lateral thinking. So I went into the data folder and found that two pilots were listed. I removed the second one from the list. It worked. The second pilot was attached to some kind of carrier parking system, much of which had been stricken out. So now the gay pilot has gone, it's working. And since it's a fine cockpit, I'll spend some time on customizing it to my screen size and preferences. The graphics are really excellent, and unlike the SF1 Harrier plus, the nozzle gauge syncs perfectly with my controller, so I can actually get 110 braking. Meanwhile, I fired up the EF2000, and at some time in the mission I dropped the centre tank. Imagine my surprise when I checked the outside view and could see a set of stowaway legs sticking down from where the tank had been. Once again, there was a second pilot I had to strike out.
  15. I couldn't get this to work. I put the aircraft in the aircraft folder and the fake pilot in the pilot folder, in the users mod location like you are supposed to. I tried this separately in both Strike Fighters2 and Strike Fighters 2 North Atlantic. And I tried on two separate computers. But when I get in the cockpit , my view is of the back of another pilot!!! In the outside view, there are two pilots in the cockpit, one sat on the other's knee. I'm the one at the back. It's all a bit gay. I'd like this to work because I have quite a few items of Marina Militare clothing with the AV8B patches all over; Wolves of the Sea and all that, so what am I doing wrong?
  16. Thank you, gentlemen. It's as I suspected, but I love your replies.
  17. How does my wingman know that I "got one"? I'm flying the stock F-14 in SF2NA; I have four targets on the Radar just coming into range of the Phoenix. I have already designated each target with a phoenix. I launch each phoenix, and wait. After a short while my wingman says "Ya got one", Good shot", "You're awesome"," Will you marry me?".( I think I made some of those up). That's how I know I hit the target. But how does he know? I can't visually target them because they are too far away. I could watch the missiles going in, but that's cheating. How do I know the kills happened, other than some time after my wingman has given the game away, the radar shows spinning targets?
  18. SF2 A-6E VA-85 Black Falcons for Third Wire A-6 Intruder

    This would be okay if the black blob fuel tanks could be removed. This is clearly a glitch.
  19. My aircraft is also showing black blob fuel tanks on every hardpoint, even when you haven't loaded fuel tanks. When you load weapons, they superimpose over the fuel tanks, and then as you fire the weapons the black blobs are left on your plane. I notice the last support comment was made in 2011, so obviously no solution to the problem. Maybe best not to look at aircraft from outside.
  20. The excuse is that I have several FLIGHTDATA folders in the FLIGHT folder. They are named for Different aircraft. So FLIGHTDATA_A-6A, FLIGHTDATA_A-7E etc In each FLIGHTDATA folder is a HUD.ini for that particular aircraft. Some have Radar pop-ups, some RWR pop-ups, some have both, all particularly tailored to a specific aircraft. So if I'm going to fly the A-6A, I just grab the HUDDATA.ini out of the FLIGHTDATA_A-6A folder and overwrite the current file. Should have created a FLIGHT folder, but had FLIGHTDATA in my head.
  21. Are extracted files used in a different way in SF2 than in SF1? And is SF2 North Atlantic even more different? I have the April 3rd wire tools downloaded. I extracted the HUD.ini from SF2NA in order to reduce the size of the on-screen text. In SF2NA it looks massive on my 27" screen in 1920x1080. I altered the HUD.ini to give a smaller font. I placed the altered HUD.ini in the FLIGHT folder of SF2NA as I always did with extracted SF1 files in the SF1 FLIGHT folder. Nothing changed. What am I doing wrong, please?
  22. Thanks that's a good tip. I'm new to SF2. My WinXP machine went AWOL, so I'm now on Win 10 and SF2 runs perfectly. So a lot of catching up to do. Confession: I called the new Folder "FlightData", not "Flight". So my bad.
  23. Yes, I tried that. I created a FLIGHT folder in the User/SavedGames/ThirdWire/StrikeFighters2 folder, because there wasn't a FLIGHT folder. I extracted the HUDDATA.ini and placed it in that FLIGHT folder. Then I modified the HUDDATA.ini. Nothing changed in the game. But when I moved the HUDDATA.ini out of the FLIGHT folder, and left it in the main User/SavedGames/ThirdWire/StrikeFighters2 folder, it worked. Based on what you're saying, if I modify the Cockpit.ini of the F-14, I should put it in User/SavedGames/ThirdWire/StrikeFighters2/Objects/F-14? And I'm assuming that if I download a new SF2 aircraft, I should put it in User/SavedGames/ThirdWire/StrikeFighters2/Objects. I can see the logic of the new mod structure. It's very clever. Thank you
  24. Actually, that looks like the cockpit I'm using in the B-1B. I'm sure it came with the B-1B. Terrific cockpit anyway.
  25. I'm running win 10, 64 with an nvidia GTX 1060. WOV ran at 10 fps. I then read about the HDR Mod 1.01A, installed it and I now get 58 fps (the numbers flash because they can't display higher). I installed the game on an XP machine first, then copied it to the win 10, because the win 10 wouldn't recognise the disc. I run compatibility win XP service pack 2 and run as administrator. It works for WOV and WOE. Sometimes I get a crash or freeze after a mission, but the important thing is that I get to fly the mission. I tried it on a newer 16 series Nvidia and it did not work at all. So the GT 1060 is the graphic card of choice.
×

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