Jump to content

Cougar

Members
  • Posts

    1247
  • Joined

  • Last visited

Everything posted by Cougar

  1. http://hyperfighter.sk is the new addy but its down
  2. then you will soon complain if theres bugs lol
  3. It might be your profile in itself, I uploaded my old TIR profile that I used with my TIR 2 might work. LockOn.zip
  4. Did you delete them from the beta version or the official release?
  5. The Angle of line ;) Now i got what ya mean, well from that angle yea it look offset a bit but if you turn right to center the steering dot in your hud it does match together.
  6. If we are talking about the steering dot, it changed a bit, it travel less then it used to so basicaly when you are in range but out of the FOV of the missile the steering dot will be out of the circle and wont have the launch light. The steering dot stays at the same place on the radar or the hud as it helps you have the best solution angle to shoot on that target. Changing the range on your radar doesnt affect where the steering dot will appear as if you change the range the target distance wont change. So like in your example you have your radar set at 40nm, you have a target locked at 25 nm ~30 degrees offset to your right and his altitude is 3.7k. You are at angel 38.7 so the steering dot tells you that your best angle to shoot that target is right and a little bit down (~4 oclock position). If you change the range to 20nm, you will see that the steering dot is still at the same place but the target doesnt appear on your radar as it didnt enter the scan zone youve selected. If you select 80nm you will see that the target is below the steering dot so like I said range doesnt affect the steering dot. I hope I didnt confuse you and hope it clear it up for you Cougar
  7. You need to take in consideration that you are high, your target is low. you are banking right and hes offset 30 degrees to your right
  8. Well I see both pointing at 4 oclock or to your right so nothing is wrong here.
  9. Well explain more your problem, there were no AI planes in the mission, so you got problem with human planes or it was with sams? As an alternative for now you can clear up the TEWS with shift - r
  10. I do think its a bug but until ED investigate this nothing is official :)
  11. I would say more like AI related instead of only SP ;)
  12. Why start another thread about a bug when theres a section up there saying Bugs?
  13. Im only a beta tester so I have no power in all this :) ED will have a look at this probably monday, so until then people can use the "Shift-R" combination to reset there TEWS RWR.
  14. Yep will see Monday what will happen gents, thank you for reporting this problem I guess we arent perfect ;)
  15. Rgr that Iguana, its a bug either way I even tested it so we missed that one :(
  16. You have the default track that is located in your temp folder? If not then its because you restarted the game and without the default track its hard to pinpoint the problem.
  17. Ok, are these happening online or in single player mission or both?
  18. And maybe redownload 1.12 as it might corrupted itself, just a thought.
  19. Use the starforce utility to save your registration key and put it on your desktop. Remove lockon and delete the folder too. Reinstall the game, 1.0 1.1 then 1.12 and when you are done, put the key into your lockon folder and execute it and you should be set. Also it might help the spike problem.
  20. Nah I was just wondering, I would need to relook it but arround sochi AF I saw the texture on but earlier I was flying over krimsk and I didnt saw the runway texture. I will give a look later and report back here.
  21. If you installed 1.12 you should have a 1.12 readme in there :)
  22. Alright well try a Fresh install, 1.0 1.1 1.12 Then report back, ty
  23. Have you done all the runways on the map or only a particular sector? Thank You
  24. Well happy ending ;)
×
×
  • Create New...