Jump to content

McDaniel

Members
  • Posts

    239
  • Joined

  • Last visited

1 Follower

About McDaniel

  • Birthday 04/18/1975

Personal Information

  • Flight Simulators
    DCS, IL2, Falcon BMS, MSFS2020
  • Location
    Switzerland
  • Interests
    Aviation

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Or use sidequest and disable proximity sensor... the headset will always be on...drawback battery life McD Out
  2. Thank you, please make it a priority before adding new stuff.
  3. Hello community I was not very active in the VR region because so far the visual quality did not meet my expectations. I had a Rift cv1, Rifts S, Quest 2 and now a Quest 3, it's starting to get acceptable to my expectations. Another reason for my hesitation is my mediumcore Simpit, Winwing MFD's etc. But the past few days I could test some settings and was amazed, how well Virtual Desktop works with DCS. The best part was the OpenXRToolkit Turbo Modus, it's working absolutely hassle free in Virtual Desktop, I can switch Turbo Mode on/off without a problem. QuestLink with Cable is a different story, I could not get Turbo Mode to work, it was always crashing. I found a workaround, if I enable Turbo Mode with VD, I can use Turbo Mode also with the Link Cable, but you must disable the proximity sensor in the Quest3, in other words, the headset must run all the time or DCS crashes if you take the headset off. You can disable the proximity sensor with sidequest per software. Also you cannot switch turbo mode with Linkcable, if you switch it off then you need to enable it again via VD. Maybe it helps someone to know. You may ask why the workaround, just use VD. With the LinkCable I can use the headset in DCS as headphone and have the bitching betty or other stuff just in my headset, while I use a strong 5.1 System around me. I could not get it to work like this in VD. Mr. mbucchia, first thank you for all the work. TURBO MODE is the best, it gives me such a smooth experience, I wish I could have it everywhere, VR, 2D etc. I hope you are not abandoning this "Technic/Strategy". Tank you McDan out
  4. Can somebody please report how it is after the patch today? I am away, can't test. Thank you
  5. Hey mbucchia, thank you for all the hard work for our community . I tried your quad views yesterday with my quest 3 on rtx 4090 and amd 7800x3d. It gave me the smoothest vr experience ever in DCS. No jitters, no stutters, nothing...as long I could hold 72fps, a dream to fly the apache so fluid, gives me total control and immersion. I am not very technical, I don't understand, why quad views uses more GPU power, but is so much smoother then without it? In other words, with quad views, I had less headroom, then without it, but the experience was much smoother. What is the difference in using quad views or using foveated rendering in the toolkit? I know stupid question, where does the smoothness come from? I really thought it's not possible with dcs mt version. Is the solution with Virtual Desktop, the same technology, is it as smooth as quad views? Kind regards McDan
  6. Hmm, I always have been very understanding and supportive in the development of the AH-64, I do understand, it's still wip. Since 2.9 I can't use the module anymore without beeing annoyed by the skills George displays. As I fly alone, I really need him to perform to get anything done in a serious manner. So please fix this somehow sneeked in bug asap. My AH-64 is grounded McDan out
  7. Thank you for saving me, had exactly the same issue, force feed back was activated...unticked all solved I installed some software for my simracingpit, maybe that somehow triggered FB in DCS...
  8. That's the explanation, I was doing sp mission and let Georg to the hoovering and I took the shots, worked perfectly...so I was ready for some MP action, I did the flying, no hoovering, and George the shooting...missed almost every shot so I guess I need to try hoovering.
  9. Ok solved my problem with Quest 2. Because I never use the headset other then on my link cable for simulation, I totally forgot to update my headset. I am talking about the headset not the ocolus app. I connected the headset to wifi and updated the software on the headset and voilà it's working with Mt.
  10. Same here...is there really no solution yet?
  11. Thank you, you mean I should start it like a server for myself? I guess , not like a single player mission. How can I test lag?
  12. Hey Pilot's I know about the performance difference between SP vs MP, but I just can't deal with the Stutters, which are not GPU induced. So I tried and downloaded a heavy scripted multiplayer mission and used in Singleplayer...no surprise, absolutely smooth and stutter free. If I play the same mission in multiplayer it's over with butter smooth...I know it's more demanding because of the other player's, but my GPU is at 45% with locked 60 fps, which never dip in MP. CPU between 14%-25% Are there any tweaks to make the multiplayer experience more smooth? Do I miss something here? Are the Stutters CPU induced or by lag from other players? Thank you McDan out
  13. See now you already know Had the same problem, it's because you altered some lua's, like labels or something else... Use the repair function of dcs, after the repair, my hud was back to normal. But be aware of all the skins and mods you added, you will lose them, but you have the ability to back them up in repair. McDan out
  14. Did the latest AH64 update bring the possibility to remove the robbie tank? McDan out
×
×
  • Create New...