Gun Jam

I do have win 11. I gave online a shot. I tried halfganistan first on TTI but it ran out of time. Then switched to PG TTI. I probably got close to 20 min of up time and then the display froze. DCS was still running and functional on a core level. I could hear all my inputs working and the sim running but the display was frozen then after a bit dropped back to the pimax play home screen was very laggy. But dcs was still running... I killed dcs with end task. It never officially crashed. any clues in this log file? dcs.log

I have. Someone on the crash section of this forum provided me with some tips. Ill let you know if they help. SO far it seems improved....

This is the best its ever run with the super. so far, its exceeding expectations and seems stable. this maybe dialed in now from a "this is a solid starting point" Ill let you know if it stays fixed. Thanks

Interesting I thought I unparked the cores. Ill look into all this. Thanks!

Here is the latest Log file. I looked though it but can tell what item might be related to the crash. Thanks! dcs.log

So SSAO on VS off looks the same to you? And yes it is 100% a QV issue. However I'm quite surprised that SSAO "on" made no change on your end.

In my case it significantly reduced the issue. but I can still see it. Turn SSAO on and see if its worse.

@Calvin.Pimax Ive been doing what I can to get pimaxplay 1.41.2 to run DCS with quadviews. I have multiple issues with DCS crashing that appear related to quadviews. Im using only quadviews within PP. I have uninstalled the openrx items. 1) without quadviews I get a pretty soil 35fps and DCS seems crash free. (im using syria instant action f14 takeoff from turkey the night one as a test) 2) with quadviews I get a pretty solid 35 fps or 60fps or 85 fps it just depends on how it feels during that launch I guess I cant find anything related to this not even resolution / global settings vs game settings. More resolution I get maybe 85 fps then i dial it back and I get 35 fps 2) with quadviews running like crap (35 fps) and settings low say 70% render resolution dcs wont crash or wont crash quickly. 3) with quadviews running great like 80-90 fps at 100 or 150% render resolution It usually crashes in a minute to 10 minutes or on final load screen just before you click "fly" or whatever with the background and cockpit visible behind that window. there is no consistency or obvious pattern to which outcome im going to get. Is there anything I can submit or provide you that could help isolate this issue?

Thank you for the suggestions. I finally had a chance to follow your suggested fixes. I set the game launch to DCS inside bin I cleared metashaders2 and fxo folders from /user /savedgames / dcs (or something very close to that path) I then attempted to run DCS with DFR from pimax play and now it hangs right as the cockpit textures start to load (I was trying the instant action for f14 BFM cat and eagle) I dont get a crash report but it does appear to freeze and shows no sign of unfreezing. I ran slow repair that did not change anything (did find some dlss files that it put in a backup folder I tried using the bin mt exe that made no change. This did for sure change how it acts... But it made it worse still seems to load okay with DFR turned off in pimax play. Thanks!

Oh what... No way, here i was thinking I was about to be cool

yeah.... Nice! I read that story to my students. I make em sit though it

all these random new females bringing up old or dead thread with a new account that has 2 post... Obviously DCS is becoming a thing that women like now! Nice.

Probably nothing. Im new to the whole DFR and pimax thing. Ive found all versions to have some serious issue. I cant get consistent results from anything yet and I cant figure out how to replicate or reproduce problems or stop them lol. with PP latest 1.41.2 I did get it to run at 75 to 90 fps several times but its also crashing still and sometimes will revert back to running at only 35fps. It all seems highly correlated to mbucchas quadviews its complex... lots of combos.

I think its an issue with pimax play (PP) and Mbuccha's quadviews. I cant get native PP quadviews to run past 30fps but cant get PP to run DCS reliably with Mbuccha quadviews which gives me around 80 to 90 fps. Am working on this. Thanks!

@Calvin.Pimax In order to help trouble shoot the crashing issue I simply enabled quadviews within PP its my understanding that they overwrite the mbuccha quadviews. I was expecting to fly around at 30fps but wanted to see if it would crash. to my surprise I was getting the same FPS as with mbucca's QV 1) I dont know why its working now 2) I havent figured out how to replicate the issue yet 3) This seems to have stopped the constant crashing will keep testing this Thanks!

Ive been using the G2 and DCS has been running reliably. about 4 days ago I setup a new crystal super and it seems to be progressively crashing more and more often. My lizard brain says its a broken cable that is disconnecting with head movement. I have no proof of this and it seems to not do it in menus or "test" environments so its probably something else but it feels like a bad cable. Sometimes I get 20 to 40 min sometimes I get just a few min sometimes straight away. usually crashes making large head movements usually looking down and then back up. The display will freeze on the last good frame it sounds like the core and background stuff is still working. I can hear the jet respond to inputs but display output is frozen. Ive attached a log from Syria free flight f14 take off from Lebanon ( I think the one just before sunrise) I saw nothing of value in the log but I might not be looking in the right spot. Any clues?? Thanks! dcs.log

@Calvin.Pimax Im having almost the exact same issue. 1) I started out with 4.41.2 and nothing else. 2) i used Quadviews in PP only and right away got a good 75ish FPS on the ground and about 85 to 90 in the air. It was working well. 3) I tried some other setting only within PP like using "start" in the games tab within the "DCS" game after making setting adjustments. I also tried "smart smoothing" and lock to half frame rate. 4) after doing the steps describe in 3 FPS dropped to 35 and was not usable. I could not solve this problem by reversing the settings. I gave up and installed 1.40.4 and quadviews. This ran great (at least as good as in step 2) but DCS would crash frequently. 5) I switched back to 4.41.2 and tried only the PP quadviews. same problem 35 fps. Reinstalled (repair option) mbuccha quadviews and using that I get 75-90 fps again. 6) but dcs still seems to crash a lot. Im worried its a cable issue. am investigating.

I just started using DFR and this is a bit of a problem. Im hoping this can be addressed! this doesn't look too promising though.

While this did not eliminate the problem it reduced it to the point where its no longer WAY worse than the expected amount of mura. It is now just barely more noticeable than the mura (which is not bad... well coming from a g2 anyhow) It can now be forgotten after a few minutes and wont remind you its there every time you check gauges. Wish it was gone but this will suffice for now. Thank you!

I have version 1.41.2 Using quadviews If I want to supersample the Foveated section in the center of the FOV to 150% is the following the correct method? Note: "Gaze area resolution" can not be set past 100. This would be the logical way to supersample the foveated part of the display... but no. 1) Set image quality "CUSTOM" set slider to 150% 2) Set quadviews "Gaze area resolution to 100% This means that the whole image is now 150% boosted and I would have to reduce "peripheral area resolution" by 50% to get it back to the same value as it was when "set image quality" was at 100%??? Is this the proper way to SS the foveated section in PP? Thanks!

When you guys use quadviews with the VR1 do you notice a square that follows your vision in the center of the FOV? Is that a quadviews issue or a dcs issue or something else?

Yeah the mura thing is blown out of proportion. I see it but its not a problem its about 10x less noticeable vs the square, which is why I thought it was funny. Lets worry about this nothing item and totally ignore a very noticeable visual anomaly Im still really impressed with the eye tracking thats a huge win a 10/10 so far.. So thats awesome!

Ohh okay. I should ask the guys with the VR1 if they notice it. I'm hoping at some point it can be resolved. People are losing their **** over mura and prospective buyers are totally freaking out worried its a deal breaker and then everyone failing to notice this huge square in the center of their FOV? why am I the first to discuss this... where were all the pro reviewers on this topic... oh yeah spending time worrying about mura

@eFirehawk your VR1 Experience is pretty identical. I also could not get eye tracking to work well with the VR1 I could get it to work if your eyes were super close to the lens and it would be good but if you moved the headset calibration was proper ****ed at that point and it was game over trying to get any tracking needs dialed. A few members here seem to have got the VR1 to work well for them so thats awesome for them. The Super is awesome. I got eyetracking working late last night and its perfect, move the headset its fine, calibrated once and it seems good to go. Even not fitting well eye tracking seems to work great. I did get an unofficial 126 horizontal and 100V with TestHmd. Ive got to work with the fit a bit more. I could not test the VR1 because it did not have controllers and I didn't have lighthouse controllers and I wasn't buying them just for that thing.

Ive got this running pretty well using the latest PP software. There are some issues to work out but my first question 1) DFR and pimax eyetracking is awesome. It actually calibrates no problem and tracking seems almost flawless even when lifting up the headset to type something, it seems to track perfect after putting it back on. 2) The question is the square in the center of the FOV when using DFR. I thought this was just in the mirror window I didn't realize it was visible in the headset. I wish it would go away, it looks like a debug feature to check if DFR and eye tracking is working. Are we stuck with it? Why does it exist (what causes it) why dont I see it in the dcs menu? if it cant be removed can it be reduced? I find it pretty distracting. Thanks!