跳转到帖子

RogueRunner

Members
  • 帖子数

    666
  • 注册日期

  • 上次访问

RogueRunner 发布的所有帖子

  1. doesn't work, OA1 or OA2 you can cycle only to wpt 25, not higher. Also cannot enter something higher than 25 via the ICP
  2. Seems you cannot use waypoints higher than 25 to create OAP's Is that a feature? My thinking is to create an OAP for something I cannot see but I know it's brg/distance from something I can see. The quickest way would be via a markpoint
  3. mine did the same. After a clean install still crashed and after about the 3rd time I removed the saved games folder it just started up again. I have no idea what changed.
  4. I looked at the traffic on my dedicated server and I see traffic to one specific IP (138.201.206.135) on port 8090 only when the server is running. Nowhere can I find documents why the server is trying to talk to this IP on this port. Is this known traffic or must I investigate further?
  5. That is a VRAM issue. You get that bar at the bottom on the quest 2 when you run out of VRAM. The Q2 does not recover VRAM when it's not needed anymore. Only thing really is sto restart the game. Some people said a ALT TAB to another task and back solve it for them.
  6. Is this suppose to work? Tried testing it tonight. Could not get it to work. The Voice chat window would not even show the frequencies for the radios until you move the mode dial all the way to G and then back to M. If it does work could someone post a quick guide?
  7. A refresher flight we did on the SAAF discord last night. Just some navigation, AAR and using offset waypoint to drop bombs.
  8. I also like to know. Everybody falls back to ground attack points and such. From a pure navigation point of view, in the Mirage for instance you can tune to a TACAN channel and create an offset for 200 degress and 70nm and the INS will give you steering to follow to reach that point. Navigation beacons in the DCS world is sparse so it makes sense to make offset waypoints to enter a valley or some other point you want to fly to. The Viper OA1 and OA2 can do this for waypoints but you can only enter feet which obviously makes the range an issue, you would most likely only be able to put in a few miles at best. EDIT I guess with modern systems you do not need this much, it pertains more to older INS systems. Would still have been nice to do, for example if you get a bullseye call ffrom GCI for ground targets it would have been easy to program the offset from bullseye to get to that target
  9. i suppose the 8GB limit is not a *thing* anymore with the release of South Atlantic. Nevada is a very nice map to fly around I must say.
  10. How is this used in a mission when placed with the ME?
  11. ??? Most mods being released now is from the cold war period. I do not see the Lancer compete against modern era jets but more in a 3rd world conflict scenario where both sides have aging and semi modern fighters. The Lancer vs Mirage F1M would be a nice scenario
  12. I would love a Mig21 Lancer in DCS.
  13. This actually happened to me today aswell. After a repair, I aligned again until align flashing on the HUD. Bombs wasn't dropping close to where they were supposed to.
  14. I think most people play DCS for the fun and enjoyment and not to be the best ace on every server. For me there is no going back from VR and I would rather not play than go back to a tracker, lucky we have alternative now. Anyway, it completely porked my performance. Pretty much went to 1/2 what it was. Hope there is some sort of reprieve soon.
  15. It's 1/2 what it was! Used virtual desktop before with my Q2 in 90hz and I had solid 45frames per eye on Syria above Ramad David. After the update virtual desktop + Steamvr it hovers in the 20's per eye. Changed to Openxr and with that and the Oculus app it varies wildly but the number I see the most constant is 27 Really really disappointed!
  16. In the past I could launch DCS using the oculus app or more recently using Virtual Desktop and then launching DCS in there. Never needed SteamVR until today.
  17. Using a Q2. Since the patch DCS insists on loading SteamVR when I start it up. Is that a requirement now?
  18. It isn't really, once you used it a couple times very quick to add a new waypoint
  19. My Tacview is not writing files to my disk. Checked the export lua and I can see the game create a tacview file in documents but when I close the session the file is deleted.
  20. Does this release fix Vaicom in 2.8 or is the community patch still needed?
  21. Saw something odd with the F16 GM radar. Pretty sure it was not like that before. Looking at Tunb island this weekend, it wasn't rendering nicely to start with but also when I moved the cursor, the island would move with the cursor and then sometimes 'snapped' either back where it was or would move to the offset. I will try to make a short video tonight.
  22. Where can I get this file? Not part of that discord.
  23. Not working for me, even with the new version. Window comes up with C + S + x but cannot import coordinates from the F10 map. Do I need to leave the old scratchpad directory and the scratchpad-hook file in scripts or delete those? \\When I delete the 'old' files the windows doesn not even come up for me EDIT: seems to hotkey changed at some point, mine was still CTRL + SHT + x but it's now 'w'. Works perfectly thank you!
  24. Q2 VR went from a constant 45fps per eye (headset running at 90hz) to 39-41 over Ramad David and with a noticable 'flicker' when you roll the jet with full stick deflection and looking at your 3-9. Was silk smooth in previous version. Haven't tested Vaicom yet but read it's broken too which would be a bummer as well!
×
×
  • 创建新的...