All Activity

Hi team, I am nearly 2 weeks into my new Crystal light upgrade from RIft S. I cannot get a setting to work. I have followed everyones online setup tips. I have tried native 72,90 and 120hz. I have tried all the quadviews and priority rendering on/off. I ideally would like 120hz locked to half, but if I try this on pimax play and/or in DCS the visuals are so blurry. Any variation of HZ halved is horrible. I can get a lovely clear image with 72hz and tweaking Quadviews and priority rendering, but lots of micro stutters ruin this. Smart smoothing helps a bit with this, but then seems to cause FPS to drop causing other problems. I have literally gone through every combo of setting with out a smooth clear experience. If i drop all the DCS in game settings to low, I get the same experience. I had online assistance with tech help the other night and they noticed from my logs that the headset had instances of not acknowledging settings from pimax play. We did some rectification by deleting logs and files and opening Pimax Play in admin mode. But none of this helped. And now to top it off the quadviews wont work at all. I select it on and can chose any of the 4 options, but the headset clearly isn't applying them. Tonight in the Pimax "space" scene I notice that if I turn my head left to right its stuttering very slightly. And if I focus on an object, I turn more than around 10 degrees, it goes out of focus. Now have a ticket open and am waiting further instruction.... I only use Pimax Play, no openxr or independent quad view. Is this the issue? Using lates version 1.0.18 firmware and Play version 1.42.1. System: Windows 11 Asus Z790 Nvidia RTX 4090 I7 14700K DDR5 64mb 6000Mt Drives are Samsung SSD 980 Pros

There's one way not tied to the WinWIng software, few posts below there's also a WinWing software way

I meant to be a little snarky, and maybe even a little self-deprecating as well, but it wasn't my intention to be an outright dick or make fun of you. My apologies for that. I thought only the French get offended when you don't speak their language? While I find it slightly inconvenient when I need a translator, I wasn't "offended" in any real sense of that word, nor did I view it as any breach of respect. I'm pretty sure the guy wasn't writing in Spanish to be a troll or piss anyone off, and he apologized for the inconvenience. It isn't a big deal, and everything is fine.

Depending on the "Force IDP Distance" value in the VR settings, the helmet visor display shifts/deforms. The last value at which the visor covers both eyes in VR is about 75 for me. Anything higher doesn't work and shifts. It looks like the visor is centered only on the right eye. For example, the attached screen at a value of 100. I don't even know if this is a bug...? If so, please check. I assume that like the helmet sight, it is set to display in the right eye by default... maybe it will be necessary to set a default value for both eyes for its display? Selecting the display like in the case of the sight would not make sense...

Any plans yet to add support for MiG-29A Fulcrum module in Simshaker for Aviators? How does it work for you? On my end it doesn't work (on final verson 2.9.0.0) What software version are you using?

True but I consider that a mid service upgrade. But is is true that the German Planes are 9.12A's so i would be fine if later on down the road we might get it, but i don't think it's something we should really expect.

That’s strange. HDR is working for me. can you redo the steps here https://forum.dcs.world/topic/356128-reshade-vr-enhancer-mod-vrem/page/15/#findComment-5696048 with HDR on and post files ?

Not fixed in 2.9.20.15384. @BIGNEWY This core bug has persisted for 3 consecutive versions, so I presume it has flown under the radar.

... then you wouldn't call it "MiG-29A 9.12A" since that doesn't exist: an aircraft can't be 9.11 and 9.12A at the same time, especially since 9.11 never materialised and was just an idea abandoned in 1976

Yes, this is my solution in response to player requests. Several people wrote to me that the ships are hard to find, and it would be nice to mark them with smoke. The eternal search for a happy medium between DCS veterans and newcomers.

Not fixed in 2.9.20.15384. @BIGNEWY This core bug has persisted for 3 consecutive versions, so I presume it has flown under the radar.

Forgive me. I was mistaken. I'm too busy working with the Outpost campaign series. I was trying to test this method and completely forgot that the MAD KA-50 doesn't have Russian voiceover. Sorry for misleading you. There are no Russian voiceovers here. https://www.digitalcombatsimulator.com/en/shop/campaigns/mad_black_shark_campaign/ https://store.steampowered.com/app/2635100/DCS_MAD_Black_Shark_Campaign_by_Stone_Sky/ I checked - it is indicated correctly. Russian voiceovers are only available in MAD, MAD JF-17.

Hi there, I'm encountering the System.ArgumentOutOfRangeException . File seems OK with actual information of the flight, it will be great if you can have a look at it Thank you! (forgot to say that server crashed before finishing the flight) debrief.log

There is no help. It's been doing that in VR for a long time when you go to the F10 map and then back to the cockpit. Quite annoying...yes.

Where did you hear auto mode changes PRF for target aspect? It should just change randomly every second or so, meaning it might not hold long range locks or short range where there isn’t enough closure. 2. P mode has quirks, you can easily get locks to 30-35 km but you need to be above about 3 km altitude. Below 3 km altitude its lock range quickly decreases to 20 km or even less at very low altitude. When range becomes close, especially above 3 km altitude, P is the best mode to turn an STT lock to or engage STT when range decreases to 30 km or less. It can have a smaller notch and you’re only way to receding targets.

Quad view targets and Target region are set to all or all views in both places.

Still waiting for a track please.

I hope we will get more of them "soon"

I appreciate the suggestion. If this does end up in the sim, it should however be in a backwards-compatible manner.

I agree with your wish for coherence, but still, the fact that we can chose between metric and imperial should be maintained. The MiG-29Gs were former MiG-29A (9-12A) that were converted to english/imperial and only very "moderate" changes on top of that. If I were nitpicky, I could as well say that it is unrealistic to fly the DCS MiG-29 with soviet liveries, because the announcement clearly states, that it simulates the Warsaw Pact export version (9-12A as opposed to the regular 9-12). Oh...and in that case also: AA-10C (R-27ER) and AA-10D (R-27ET)...nope...unrealistic.... See where we are getting with this?

Sorry, can you include a short track on Caucasus? Works fine in public version with localizer and glideslope indications on the ADI. The bank and steering indications should only operate in Approach and Automatic Landing mode. We are not having much luck replicating this. Thanks!

I'm sure I did this before on another jet but currently the AB kicks in about half way up the travel of my WinWing throttle. How can I match that to the actual afterburner detent on my WinWing?

Exactly 3 seconds!!!!!

disable the power service (and every other background process you can live without). The .1 lows are mostly caused by interrupt calls from other processes. The power service is one of the big offenders and easy to live without with. I suppose you have disabled the AV already.

Yes, and the Germans explicitly modified theirs for wing tanks