Jump to content

RafaPolit

Members
  • Posts

    337
  • Joined

  • Last visited

1 Follower

About RafaPolit

  • Birthday 07/13/1977

Personal Information

  • Flight Simulators
    DCS World
  • Location
    Quito, Ecuador

Recent Profile Visitors

1623 profile views
  1. Ok, sorry, misunderstood the terminology. I see what you want me to do. Actually, I have only ever had "double tapped" to Passthrough, not to the desktop. I'll try and see. but still, the fact that it can get recovered is no supplement to actually "unfreezing" by itself, as if you are in the middle of a dogfight, at dive toss, a landing, etc... by the time you grab your controllers, double tap out, open the menu and return to the game, you are already dead.
  2. Not sure I understand what is this button to slide out of the VD menu? Thanks for any clarification.
  3. My pain point is that, as of last time I tried, VD works great most of the time, but it comes a moment where the screen-cast into the Q3 gets locked into a single frame. The computer still renders the game, the Q3 is still reporting movement back to the PC, but there is no way to get the stream to sync again to the quest and there is no way to recover from it. Closing VD on the quest and reopening will get you a black screen. If you close VD from the computer your link to the game is lost. The only thing that allows these scenarios to re-sync is enabling game boost priority, but this creates recurring stutters during gameplay every couple of seconds and is really annoying.
  4. Was this using Link or VD? This trick works for the stuttering on link. In VD, the frozen screen is unrecoverable. That’s why I have given up on VD.
  5. On the Quest3 you can double-tap on the side of the headset and it will enter passthrough mode. It is a godsend in many scenarios, many of which feature my cats destroying something new around me and me double tapping out of Oculus Link, which is the only way I have found works, as the controllers meta buttons no longer have the same behavior. For me, with link (not in VD) fixes this stuttering or jerkiness. Which GPU and with which Dirvers? The VD team suggested back a few months ago that I had to block the nvidia drivers on a very old version for my troubles to disappear, but I work with my computer, sometimes with AI requirements, and I play other games, so this was not ideal for me.
  6. Sorry for the late reply. I have almost given up on VD completely, and mostly due to DCS incompatibility. It simply works perfect for X amount of minutes, and then, all of a sudden, it freezes in one frame and cannot be recovered. The game on the desktop monitor is still playing, even recognizing the headset movement, but on the headset the frame is stuck. Looks like an encoding bug or problem. Closing VD on the Quest3 simply brakes the bond between VD desktop and headset, if you reopen it you will get a black screen. VDs solution is to set game "Boost game priority", and it fixes the issue, but it than creates stutters every few seconds, which are really anoying. So, I'm back to using Cable Link and have found a few solutions and few problems that can be helped: - I run the resolution in OculusDebugTool.exe at 1 and configure DCS to have 1.3 pixel density. Going the other way around has less performance for me - I have put some fixed foveated rendering on OpenXR Toolkit Problem: - Every now and then, the Link software starts missreporting the headset movement, or gets "laggy" or "jumpy". Let me explain: it's the behavior described above as #2. What I believe is happening is that the headset is not reporting "fluid" movements like X position 1 -> 2 -> 3 -> 4 in a 4 second interval, but reports 1 -> 2 -> 1 -> 3 -> 2 -> 4. Something like that. So it appears as if I were shaking my head with twitches instead of fluent movements. Even if I close the game, this keeps happening in the link home screen (the one in the white infinite grid). Solution: - I have found that if I double-tap myself out of the Quest game and into passthrough mode and quickly double-tap myself in, this problem is resolved and I get fluent movement once more. I found this out by chance, since I had to stop the jerkiness as I was getting sick, and when I returned to the game it was fixed. It's a pain to do it and brakes immersion, but beats by a mile the alternative with VD to simply close the game and lose all the progress made. By the way, all this I'm describing is exclusively playing your and Baltic's campaigns, so it's a privilege to interact with you as you are my source of entertaining in this game. Thanks a lot! Best regards, Rafa.
  7. That’s my concern! No acknowledgment that they are aware of correcting this issue. Since (I assume) mostly affects lower end systems, I’m afraid it’s going to slip through the cracks.
  8. Exactly, I had to resolve to F10 a couple of times to figure out which one was him. Maybe I need to learn how to use the IFF and data link in the new implementations. For the tanker, you also need to be on PRI 12 when 3-3 commands the change of frequency. And using radio 1, f course. edit: these are shortcomings as a pilot and navigator, I’m not complaining about the mission, I’m sure this is exactly the type of ability pilots need to learn.
  9. As always, thanks for this incredible mission. So much fun! Quite a bit to do. I was wondering, how do you guys fly the mission's night scenario to ensure you are in formation with Weasel 33? Are you just that good at flying formation, or are there tricks to get better SA? For me: - NVGs all the time ON - While Weasel 33 is within a few yards, all is good - If I trail a bit, a quick radar lock gives good results, but I think that radar locking a friendly is probably not ideal... - If I radar lock him, I am also completely useless in terms of picking up radar bogeys, as the radar is locked at 5NM - If I TMS-up on the HMS page, I get the octagon to keep tags on the subject, which works great when moving "straight", but when they start turning, the octagon's speed of refresh is just not good enough - Any other means? Do you just fly "loosely" towards the endpoints and don't worry about staying 1NM within Weasel 33? As for the mission, I actually flew it twice, the first one the TANKER never replied to radio calls and I was unable to refuel, got out of fuel and crashed trying to communicate with the TANKER. Here's my potential help, maybe even a "Developer's Note" worth it? Since this is the first mission that requires DCS comms, "reminding" pilots about the non-easy comms and its implications may be useful? As it was, I was just hitting the \ and calling the TANKER. With easy comms off, this doesn't work, and although DCS gives you the chance to make the call, you are using the wrong radio. You need to RALT+\ in order to actually use PRI and call the TANKER. I had completely forgot about that and waisted the entire mission. Again, great mission, I'm enjoying the campaign very much! Best, Rafa.
  10. Maybe this is related? I don't have access to my nephew's machine, I'm the one operating the MP server, but it may very well be OOM issues which are less probable on SP missions. @BIGNEWY maybe you can shed some light? Thanks.
  11. Good evening. As one just updating from FC3, where do I get the manual to understand how to use the different modes of the F-5? I'm particularly interested in the A-G radar and locking targets (if possible) and how to drop with some sort of guidance. Thanks, Rafa.
  12. Just wanted to congratulate and report the same issues as the OP. They are by no means critical... but if you truly await for the second flight to land before you, it's going to be a really long mission! Once I saw they were straight out going the wrong direction I decided to take my chances and land. For me though, after "mastering the situation", PYRO did go ahead and land before me into the right hangar. Maybe this is dependent on where you are when this happens? Anyway, congrats on the mission. It was really great and required some bringing out concepts like selecting your wingman in the SA display and hud to keep tags on them, and pinging some air contacts. I enjoyed it. Looking forward to more of it. Rafa.
  13. We experienced this same issue, and then someone in FB posted the same problem: https://www.facebook.com/groups/DigitalCombatSimulator/permalink/7637287646397186/ My nephew cannot join my MP server and it crashes every time. SP missions and instan actions seem fine.
  14. Thanks. I did the same, they suggest that I log in with my Nephew's account and make the purchase. It's not a solution, and the notion of everyone just sharing login credentials and payment options is a bit on the frustrating side to be honest. But yeah, I can see the logic of not simply just "telling" you that the other account has the module or not, that's private information. Difficult thing to solve.
×
×
  • Create New...