Czar

It is actually the single dark pixel 'speck'/'spot' placed to aid spotting without relying on units geometry from far distances. This is what's bleeding through clouds. Units 3d geometry won't bypass cloud masking. (ALL LABELS TURNED OFF, this is not related to any label or enabled aid in options) This bug is also happening against atmosphere scattering at long, VERY long distances. Bellow are both being demonstrated. It is not only ground units but all units including aircraft. In the second picture, yes there are aircraft 19nm out, but the grouping that's flat in the blue circle is a SAM site very far away.

Yes, agree, but MT still has too many bugs as of today. Hornet Air to Ground radar GMT and SEA modes having the map mode returns, units specks bleeding through clouds (you can see every unit through clouds), low refresh rate on units movements when far off including radar dishes animations having the appearance of rubber banding/teleporting. Until that happens, single threaded it is. In MT, my performance is close to flawless on a deck with F-14s statics placed along with hornets, but in ST something is up with the F-14s statics. Lots of performance drops. (I keep at 40 to 45fps locked as I dislike having frame dropping so it is at a constant fps regardless, with a plus of a PC running cold). I removed most of the statics from the Carrier deck, now having only 6 hornets and no vehicles and no Tomcats, while disabling secondary shadows regardless of GPU load (RTX 3060 12gb, running at an average of 60%) ST performance went up.

'Mostly' had with Escape From Tarkov? How many times overall with any game? Blue screens nowadays points to something very very wrong in hardware/software relationship. Overclocking can be the main suspect if that is active in your system. You should be getting no blue screens at all. I have between 300 and 400h in Tarkov and way too many in DCS World and zero BSOD with two different PCs for years, using DDR 4 Ram. Check your motherboard for any damage. See if you have pagefile activated in windows and with a generous size (10gb-30gb), no matter your physical RAM installed.

Not everyone uses axis for TDC. Some use buttons.

Check "Hear like in helmet" option in 'sounds' if it is unchecked. Perhaps your audio setup was set for that option to be turned on and it is off.

Please make the slew rate speed adjustable. Some slider on special options and such would be great. The lower value could be the previous values, the maximum or near maximum would be the current. So it would let the user to decide the ergonomics accordingly with their hardware just like the realistic Maverick slew having to depress TDC and many other options on special tabs across multiple modules. It is not really an aid as you'll lose slew speed across the screen so efficiency wise wouldn't be overpowered and wouldn't affect the simulator's realistic approach.

The Patch 2.8.4.38947 Open Beta released on April 13th fixed the issue on Single Threaded performance degradation on Super Carriers for me.

I just tested it again today. ____________________________________ SINGLE THREADED EXECUTABLE Previous patch DCS 2.8.3.37556 Open Beta: Locked 45 fps with lows of 42 fps on carrier deck looking at the stern with the tower in view. LATEST as of 1st April DCS 2.8.3.38090 Open Beta: Locked 45 fps with lows of 17 fps looking at the stern with the tower in view. Steady low 17 to 20 fps. ___________________________________ Modules used: Super Carrier DCS: F/A-18C State of player's aircraft: Partially turned on with at least one engine running and avionics operating. It is where the FPS tanks from mid 30s to 17fps only on the carrier. No AI flights taking off or landing on the aircraft carrier. Multithreaded on DCS 2.8.3.38090 Open Beta is constant 45 fps with drops to 42 when panning from the bow to stern but comes back to locked 45 fps as I have set the game to be at.

Keep in mind, we are talking about Single Treaded executable. "The vast majority" are probably running multithreaded. In Multithreaded this issue does NOT occur.

I have experienced a heavy penalty in performance on carrier decks with static units after March 22nd v2.8.3.38090 patch on Single Threaded executable. I went from cleaning up video card driver with DDU and installing the latest one, reducing graphics besides my GPU or CPU not being maxed out. I'm running DCS with modest settings at 45 fps locked through nVidia control panel. My GPU usually ranges from 40 to 80% during gameplay. With the latest DCS 2.8.3.38090 Open Beta patch my frames dropped from the usual 45fps fps on deck in ST, to around 17-20 fps when looking at the aircraft parked towards the tower. Where there are the most polygons shown and lower than 45fps average. After take off and into the mission, fps stabilized towards the cap of 45 I've set. FIX: I rolled back to March 10th DCS 2.8.3.37556 Open Beta version and the fps are back into normal. I'm running single threaded because of current MT visual glitches in the likes of units specks/dots bleeding through clouds etc...and I'm hosting co-op sessions with a friend teaching and learning air combat and situational awareness kind of deal, so immersion is key. Graphics settings attached as image. GPU: RTX 3060 12gb Vram. CPU: i3 10100 @4.3Ghz. System RAM: 40gb. Windows 11. No change in the settings fixed the issue on the latest v2.8.3.38090, only the roll back to 2.8.3.37556. I searched and have not seen any mention on performance degradation on ST (single threaded).

But with this bug/glitch is much worse. Anyone with a decent 2D setup properly and being close enough to the monitor can see everything with overcast weather with lots of clouds. The more clouds, the better you see aircraft and ground units. This breaks the experience at any serious mission based on low intel and visual training to the point of avoiding 100% MT unless is for bug checking.

Ground units are having the appearance of bleeding through/ignoring clouds on my experience as well. Down bellow, there are convoys, AAA, SAMS, unarmed units. MT version.

I did some light painting/editing on AIM-7M and AIM-120C rocket engine effects for fun and I thought of sharing it here. Based on reference images from google. It is not a mod, but an edited image.

Vortices are also offset on the KC-130.

...and still no official response. Should this be posted in another forum category to be heard?

From my current wallpaper. This photograph is in public domain. VMFA-323. You experts can analyze it further.

I was almost freaking out just now. All my modules or almost all including the hornet and Persian gulf are giving the "not authorized to be used with your account" error at the DCS launch. Now I cannot use any of my several modules of DCS even offline. What the hell is going on? Edit: It was probably a server issue that it seems to be back up now. That was a heart pounding one...

Okay. First things first, my fresh A-10C install default POV is fine (img attatched). The snapviews.lua file you need to delete should be the one in saved games folder and not the one in DCS root folder, if the issue is a result of an unwanted default view save. You can also edit the snapviews.lua file under the default view lines separately using a text editor. Furthermore, I'd recommend a repair scan on your dcs. If something on the root folder is changed it should default back in. Also delete again your snapviews.lua file under your saved games folder. This is my default view on the A-10C. If these numbers are off from your file. copying these would be a fix method. [13] = {--default view viewAngle = 75.000000,--FOV hAngle = 0.000000, vAngle = -23.000000, x_trans = 0.360000, y_trans = -0.041337, z_trans = 0.000000, rollAngle = 0.000000, }, [14] = {--default view - VR viewAngle = 75.000000,--FOV hAngle = 0.000000, vAngle = -23.000000, x_trans = 0.126000, y_trans = 0.036000, z_trans = 0.000000, rollAngle = 0.000000, Cheers

No problem. Once a view point is saved it becomes the default until you delete the saved view file under your documents OR apply a different POV with Ralt+Num0. You won't need to re apply every mission. This is interesting, I'm firing up my dcs a10c to have a look.

Hello. You can edit in your preffered starting point of view by pressing RAlt + Num0 at setting you want as default. Move your pilot head with either trackir (as seen that you dont use it), mouse or keyboard and then press RAlt+Num0 where you feel confortable. There are tons of keybinds that you can use to move your POV in the 3 main axes. I hope it helps. As in why your default looks like that. Probably an accidental view save and you are deleting the wrong file. If thats the case, either way is remedied by re editing your default view by how I explained. Cheers. Good flights

With the support of those who commented before of course, watch the link Will posted. Nitty and gritty, this is how I do: flaps half, gear and hook down before any trimming attempt. Keeping in mind that when the hornet turns, the nose sinks so when leveling out again it will be all different in trimming, so keep half the action on the stick at least. When you're feeling good and before 3nm DME, full flaps and trim her. Don't chase the speed vector with trim, you do that with power. What you trim is where your nose is pointed at which needs to be above the horizon obviously. I bet you know many of this and what I wrote may make more sense in my head than written down. Cheers and have good sorties.

Highly limited scope and certainly not the cup of tea for many of us. His opinion stands 100%.

Looks like it's user end. Is Persicus the Persian Gulf map? I currently have the Persian Gulf installed and it is all fine. Have a go on repairing your dcs installation. https://forums.eagle.ru/showthread.php?t=114030. I haven't installed NTTR yet on my machine after my previous DCS reinstallation so I can't comment on that.