Jump to content

RedeyeStorm

Members
 View Profile  See their activity

  • Posts

    548

  • Joined

  • Last visited

 Content Type 

Everything posted by RedeyeStorm

  1. RedeyeStorm
    No go for me. The gunsight is way to the right and low. With the exeption of your OpenXR settings I followed your instructions.
  2. RedeyeStorm
    Great work. I will give it a try with my Index and report. Will be a while though.
  3. RedeyeStorm
    +1 I had the same experience. My RIO had to disable flap axis for HIS pilot setup.
  4. RedeyeStorm
    @MAXsenna I do not get everything you said but the misunderstanding might lay in the VSPX. I do not use it so I need to pauze and wait for the beep. That would also explain @AtomicMysteryWeaselconfusion. If he has VSPX activated there would be no beep now but VSPX is relatively new and it may not have been there last time he used VAICOM.
  5. RedeyeStorm
    Not quit @MAXsenna. When I say ‘Chief’ and then pauze, I here a beep from vaicom that it recognized the intended recipient. Same with Overlord, Magic etc. @AtomicMysteryWeasel doesn’t hear that beep and he should. If I read it right then because vaicom doesn’t recognize the intended recipient it doesn’t carry out the command. If this correct then unfortunately I have no solution. This may be another problem all together. This sounds more like easy comms is on. In MP I have the issue I can only talk to the tower I took off from. I dial in the frequentie of another airfield but as soon as I talk the frequency jumpes back to the frequency of my take off airfield. No idea about that one either.
  6. RedeyeStorm
    Question guys, is this SP or MP? I HD this as well but only with MP where if the server allows for easy comms it ends up being ‘on’ all the time and ignors client setting. If so I suspect an ED issue.
  7. RedeyeStorm
    Good luck with your choice.
  8. RedeyeStorm
    Grumman F9F Panther Hawker Hunter F84 Thunderstreak F84 Thunderjet British Seahawk. F100 Super Sabre F105 Thunderchief Justnof the top of my hat. Any mark or version will do. No rush.
  9. RedeyeStorm
    Hi I use it for the mouse going off screen in VR but I noticed no performance increase. I7700K running at 5hz and RTX 3070
  10. RedeyeStorm
    +1
  11. RedeyeStorm
    That I think is as it should be. The SAM looses lock when you dive again and selfdestructs.
  12. RedeyeStorm
    I noticed it too. Same with a friend when we were flying Huey’s.
  13. RedeyeStorm
    Hey Deadly, I am afraid the RAT planes are ones more not flying on the Vegas map. I also checked out the Caucasus mission and there they worked fine.
  14. RedeyeStorm
    I’ll keep an eye out for it if I see it again. Mayby it was the previous mission.
  15. RedeyeStorm
    Still using the same AI though!
  16. RedeyeStorm
    I’ll try your approach and see if it improves.
  17. RedeyeStorm
    Hi Miguel here is the mission. It is a night mission. You will see that no ground attacks take place. The AI flights just follow there path and do not attack. The flight that goes in a circle is a F-16 block 52 flight. Cannot remember if it is the fligt that I am escorting or another AI F-16 flight. I have no Tacview as I do not use it. Falcon over PG_ongoing.miz
  18. RedeyeStorm
    Not VAICOM limited. The same problem occurs if you use the ‘options’ menu by clicking on it.
  19. RedeyeStorm
    Well seems we have the same experience then by your description. Lighting is odd anyway. On PG I find the airfields by looking for the dark spots. Airfield lights become only visible when your pretty close.
  20. RedeyeStorm
    Having this as well in VR. It started when I started using Reshade 5.02. New info: when I removed Reshade 5.02 problem went away.
  21. RedeyeStorm
    Hi all, When I fly at night I usually see only a few stars. When I use the NVG I see a lot of stars. Especially in the middle of the Persian Gulf I should be able to see a lot of stars on clear nights I believe. Is it just me or is everyone having this in VR? Using an Index myself.
  22. RedeyeStorm
    That is not what I mean. This happens when the AI reaches a waypoint, switches to next waypoint but cannot make the turn so the effect is it continuously tries to hit the waypoint but that waypoint lies inside the plane turn circle and the result is that AI ends up circling the waypoint. This can happen when two waypoints are too close together with a big angle like having to turn 90 degrees as an example. I hope I explained it a bit clearer now.
  23. RedeyeStorm
    Have a bug with Falcon over PG. You fly out of Al Baghda (or something like that). The airfield has two runways and the briefing reports an ILS frequency for all four directions. On the F10 map there are only two freq mentioned, one for each direction, and the frequency’s do not match the briefed freq’s. No big deal of course. Another issue that sometimes happens is that AI-flights cannot turn towards a waypoint and then start to circle the waypoint. This is usually the waypoint after the egress waypoint. The one that is pretty close to the egress point. Last one. The last couple missions where night missions. AI flights didn’t attack their targets. I know that has been an issue in the past so it is possible that ED never fixed it. As usual having a blast.
  24. RedeyeStorm
    Thanks Migual
  25. RedeyeStorm
    Will do. Okay tried the mission. Two F16, Avion 1-1 and Avion 1-4. could not talk to tower or Awacs. Saw in the editor that the calsign was Python. Changed it to Enfield and Dodge respectivly and the radio's worked.
×
×
  • Create New...