Jokkr

OK, all of a sudden Normandy 2.0 is not working. It doesn't even show in the list of available terrain maps in mission nor campaigns' Path. Owned both Channel map and Normandy 1.0. Upgraded to 2.0 by the special offer. All DLC's Normandy terrains show up as owned in steam library. They did work, but quit during a recent upgrade, timing uncertain as I've been playing Phantom multiplayer for past few months Tried refreshing the game with file refresh. any Suggestions Note I bought all terrains from Steam. They do not show up using license check on this site jokkr

Trying to understand why I should upgrade. I have FC3. I also have full fidelity F86 and F5. I assume the budget versions are fresher than full price and ff versions have stopped (permanently) all future development, ie graphics, flight models.. feel like I’m the looser here… is that correct? jokkr

Excellent work Diamond. Started off by just discarding the binding, nothing else…. everything is working fine, woo woo btw, I’m also a virpil user, stick, throttle, 2x button boxes. Great stuff rarely solved so easily thanks bud jokkr

Hmmm, that’s interesting. Will a simple unbinding solve or do I need to rebuild ?

dxdiag jokkPC.txt

dcs.20240605-193343crash log 6=5=2024.txtdcs.20240605-193343crash log 6=5=2024.txtdcs.20240605-193343crash log 6=5=2024.txt

tried the latest version uploaded this am. Still broken!! dcs.log Odd how all other aircraft i fly do not demonstrate this jokkr

I have the same issue. Also on a Quest Pro, F4 crashes upon hitting fly button. All other planes I have tried are OK' I did notice problem starting just after a Meta (auto) upgrade. dcs.log

I'm having the same issue of game crashing upon hitting "fly" on any F4 mission in VR. I did notice meta updated my software same morning before I experienced the issue. Quest Pro headset, standard Meta utilities Ryzen 5900 (12 core) Nvidia 3900 32GB 1TB+2TB nvme Quest Pro jokkr

I’ve been reading back comments. This issue has been a subject of conversation for years. It seems since it hasn’t been fixed in “years” it’s not going to be updated now , no matter the presentation of logic nor history.. ED has a rep for ignoring the community. I don’t see this changing. Sorry I brought it up,

It’s a long video. Discussion I’m referring to starts at minute (approx) 12:50 jokkr

I’m going off Greg’s analysis, I don’t want to get too deep into the weeds on alternate allied planes. the problem as I see it ie, the German side is a one trick pony, (K4). Allies have choices. jokkr

It’s the one by Greg that flys a dcs mission in the Anton. He states his research indicated we should have more power available as manifold pressures and limits are earlier war limits compared to our DCS plane sets. any chance this could be undated to help. Now A8 feels like a target when playing multiplayer. jokkr

I’m getting what I would describe as frame smearing. as I move vr headset the sharp screen goes liquid. Frame blurring. Frame timing in vr is excellent. Solid green so that issue is great Smearing between frames is unplayable at moment. I tried openXR and steam. Tried many settings, finally left it on all “auto” settings to left Steam decide. It’s fixable but… amd 5900 Nvidia 3090 32gb all aircraft, all terrains FIXED turns out the setting blur / smoothing is creating some very ugly events. Turn off blur in graphics menu.

Im having the same issue, but "only" on F14. Other modules working fine jokkr