Smokin Hole

I've tried (I think) all the solutions here with mixed success and lots of wishful placebo. The ONE consistent improvement has been to check or uncheck Fullscreen (whichever changes) and force the sim to restart. This works every time and balances out the cores nicely. To whomever above came up with that solution, THANK YOU! MT bin, Quest 3, 3080Ti, 13th gen Intel

Those of you (new-gen, hybrid Intel) suffering from this, a question. Are you having better results with MT or non-MT? Since 2.9, non-MT has run better for me (about on par with 2.8 non-MT). The affinity trick has felt like placebo—maybe worked..a little(?) but still not as good as the non-MT executable. I am really struggling to enjoy the DCS experience at the moment.

Same problem with the "Escort" mission but no game crashes. Rockets would be better. Other than that, I think the mission is fun and fits well in the campaign. Also, whatever trigger needs to be ticked in order to score a "success" is blind to me. I think we were mostly successful. See track. Mission 6 Escort.trk

I haven't gotten to M6 yet. So, no bugs for me so far. The campaign has been a hoot! "Interdiction" (M3) was a real joy. Loved seeing the F-15 take a bite our of my team.

I went back to the non-MT executable. Way better performance. Significant improvement in FPS and stutters about the same as I experienced after locking out core 8.

Thanks! I did that and also deleted the autoexec.cfg (just in case). You are right, it is different than it was before restarting. The squares are still there and I am still not a fan of them but they are MUCH smaller.

I don’t know. There is only one entry for the dots that I can find (under Gameplay). I am testing using mission 2 of the new Mi24 Revanche campaign. It has lots of helicopter and fixed-wing units flying just a few miles from the player. One helicopter departs to a tiny pixel as I would expect and want. After that though, it’s Big Squares everywhere. It’s like flying around a game of Pong! Quest 3.

The checkbox doesn't solve the problem for me. All objects look like the spaceships from the film "Arrival".

Put me in the camp as being one who thinks this new spotting is the worst thing to happen to DCS in years. Seeing giant black and grey squares flying around is a laughable immersion breaker. But reading the positive responses to the squares mean they are a positive change for many. That's great! if the autoexec.cfg workaround worked, we could all be happy. (Well OK, universal happiness in DCS is impossible. But most of us could be happy.)

That explains why I couldn't cold start in the included Red Flag Day 3 (Night) mission.

I've tried all of the solutions mentioned above and any that I've found elsewhere and I still am having this issue (including MSAA off). I'll be flying along with liquid smooth frames and there will be a little hiccup in the mission, the sort you see in any game when something taxing to the system occurs, like units spawning. The frames don't necessarily slow down but the tracking gets "partial", if that makes sense. It is VERY nausea inducing. The only solution is to double tap the headset to enable passthrough and double tap again to 3D. But because the problem occurs regularly on stressful servers like "Rotorheads", the double-tap solution is not workable. EDIT: Definitely an F10 issue for me. I've played a few missions forcing myself not to use it and had no issues (Syria). Tested again with F10. I didn't notice any problems initially but frames/tracking/tearing get progressively worse after selecting F10 once. Problems persist even to the 2D GUI. No F10, no problem. 2nd EDIT: F10 only aids the error. I get it without F10. SteamVR as my runtime improves the tracking and tearing but general performance is not as good. 3rd EDIT: Now running with the VR graphics pre-select from settings. I have a fairly high-end PC so this should work well and it does. I think I've just been asking too much based on past improvements from multi-threading. I still feel like something is hanging in memory. Otherwise the "bug" wouldn't persist all the way back into the DCS main GUI. But with lowered settings it doesn't interfere with my gameplay.

I have the same (or similar) issue. It is always preceded by the types of pauses you get when scenery loads or new units spawn. With the Quest 2 there is a slight loss of tracking, even once the framerates return to normal. The tracking loss is partial. If I go to F10 and move my head side-to-side, the map appears to move with my head a centimeter or two. I can almost always get the tracking back by enabling passthrough and immediately returning to 3d. I haven't tried delating shaders or disabling MSAA (currently set at 2X).

Still crashes with current A-4. Seems to consistently crash with Super Carrier when either the TACAN or MCLS are On and tuned to the correct frequency for the carrier.

Thanks! (Mine was not)

That's all. Sorry if previously reported. (Persian Gulf, on CV "Big Stick") EDIT: Actually, switching to any mode will lock the game within 1 or 2 attempts to switch. EDIT 2: See post #4 below. dcs.log dcs.log-20221103-125555.zip

This has confounded me for a year! It never happened to me in singleplayer. So I assumed it had something to do with multiplayer. Facepalm!

Stating the obvious here so hopefully I am not insulting your prior knowledge. A helicopter lift off is a 2-step process: 1st-get light on the skis and adjust controls to stay straight and level. 2nd, slowly increase the collective and left pedal as needed to a straight and stable hover. However, this only works with wheels if the parking brake is released and the tailskid is unlocked.

I am a bit late to discovering this campaign. Loving every minute of it! I've never had problems staying on the tanker before. But I realized that after an hour of pretty busy flying I need to breathe and find some zen or I easily make a mess of both tanking and trapping. The missions are that intense.

Great machine! My left flap was totally taken out by AAA. For "fun" I figured I would try to use the flaps anyway. With the right flap extended and the left flap gone, there was no apparent roll or drag asymmetry. There did seem to be some added lift as expected but I am not sure whether or not it was the equivalent or two working surfaces.

Easy fix.

I get the VAL and REC lights once I hit the position update at the IP. I do not get the BAD light. It seems to work regardless but the BAD waypoint is true to its namesake because it is always a few hundred yards off my intended target. Plus, the instant release when the trigger is pulled compounds the inaccuracy.

Hopefully Left-Cntl-N will work until we get the switch. A buddy used auto-start and that worked.

WSC Depress (I believe).

Your 3rd ballpoint references a current non-functional feature per the manual. All that is required to display a synthetic runway is that the runway lat/long be properly set up in the editor as the destination waypoint. PCA App Mode and the proper ILS frequency complete the process. Since we cannot currently place a synthetic runway ourselves with the PCN, it probably makes no difference whether or not there is a CP/PD entry.