Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

19 Neutral

1 Follower

About alexis99

Recent Profile Visitors

1,931 profile views
  1. 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.
  2. 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.
  3. This is one of those things that you think is too good to be true. But it is true. It is astonishing. I copied the WOV that I had on an XP computer and pasted the whole folder onto a Win10 computer. It ran in XP compatible mode at 20 fps with medium graphics and no cockpit. 9.5 fps with cockpit. So I downloaded the file specified in this tutorial and just did part A. With everything in graphics turned up to maximum unlimited, mirrors and all, the fps was flashing at 58 because it couldn't show any higher figures. I'm waiting for something to go wrong. This is amazing.
  4. Further to the above, I can now confirm that the F-35c lands perfectly on the Harry S Truman at 136Kts without falling through the deck.
  5. Further to the above, I swapped out the Harry S Truman and replaced it with the vanilla CV63. The A-7E lands perfectly every time without falling through the deck. Landing speed of the A-7E is around 130Kts. Maybe that's too fast for the Truman to cope with. The A-6a intruder lands at around 118 Kts, so it is slow enough to land on anything and not fall through the deck.
  6. In my experience, the A-7E has a tendency to fall through the deck on the Harry S Truman, so I fly air force missions with the A-7D instead. The A-6 Intruder never falls through the deck. Can't think of any other aircraft that has ever fallen through the deck. F-35C, F-14 all land perfectly.
  7. Will this update also bring SF1 up to windows 10?
    At last, an interceptor with a radar display just below the HUD. Magnifique!
  8. To avoid struggling to bend the "ROCKET" label, you could always go the good old air force way of using a 3-letter abbreviation, so it reads RKT - GUN - BMB. I usually do that to fit stuff on the HUD where appropriate.
  9. Thanks. I'll stick with my fix then. ;-)
  10. You know when you get an intercept mission, and you look at the map and it's 119 miles half-way to waypoint 3, and you're wondering why they didn't scramble fighters from one of the 8 airfields between you and the bad guys? Well is the best way to fix it, to go into your aircraft data file and reduce the range figures by at least half? Or is there a more sophisticated way?
  11. Talk about sledgehammer to crack a walnut. If you are talking about a fixed gunsight, you can put any mark, any digit, any letter, any graphic, on screen via the avionics file. And you can make it any colour, any size. Make sure you're 70.dll, and this is how you place a fixed gunsight on screen [HUDModeAA] (Or whichever mode you want it on) Symbol[01]=HUD_Guncross [HUD_GUNCROSS] SymbolType=Image ImageFilename=cockpit\HUD\A-7A_GUNCROSS (what the file is called and where you put it) ImageSize=0.025 (Decide how big it is) ImagePosition=0.00,0.00 (First co-ordinate -left/right, second co-ordinate -up/down) HorizontalAlignment=CENTER (co-ordinates relate to this center/center position) VerticalAlignment=CENTER Make the image position where you want it. e.: -1.45,0.17. That's left of centre, and down. You have to steal the guncross from some other aircraft and put it in your cockpit/Hud folder correctly named OR [HUDModeAA] Symbol[01]=HUD_GunsightText [HUD_GunsightText] SymbolType=TEXT TextPosition=-0.0,-0.19 (Central, but up a bit) HorizontalAlignment=CENTER VerticalAlignment=CENTER TextFormat=O (Letter "O") So your gunsight is an "O" Move it around using co-ordinates. How to change HUD Colour and font: [HUD] HUDColor=1.0,1.0,0.0,1.0 (Red, Green, Blue, intensity)(What I have there is yellow) BoresightOffset=0.0,0.0 ViewportTopLeft=-0.40,-0.37 ViewportBottomRight=0.40,0.45 GunBoresightAngle=-2 RocketBoresightAngle=-5 [HUDFont] TextFontName=Digital SF (This is a cool font. I'm also fond of Arial Narrow) TextSize=20 (How big you want it) TextBold=False (You can put "TRUE" and have it bold) You're welcome.
  12. Okay, thanks to Cliff this works now. There was nothing wrong with the file. I mistakenly put the LOD file directly in the aircraft folder, and not in the cockpit folder. It's the first time I had got a LOD, so assumed it went alongside all the INIs. My bad. Apologies all round.

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