Brother_Leb

Agreed. Map is quite hard to read as it is currently, and I think that's actually not intended. The yellow areas that cover fields near population centers appears to be some sort of error in how those textures are tagged. I.e., in the map options panel in the ME, toggling off "Towns" removes the yellow congested areas of the cities themselves but not the surrounding fields, which are mostly sparsely populated farmland. In fact, none of the toggles in the ME turn them off. It would be nice to have those large yellow areas adjusted or completely removed. With "Towns" on in ME: With "Towns" toggled off: "Sat" layer of same area: It's clear from these images that the extra yellow areas are farmland, which I don't think should be congested areas on the "Alt" layer. Thanks!

Not very interesting but... Iraq = "Iraq" Afghanistan = "Afghanistan"

Love the mod and thanks for the hard work on it! Got a HUD texture issue with the F-4C (see screenshot). The HUD pipper is orange and not transparent. Any ideas how to fix? (F-4B HUD looks fine) Thanks again!

@Dangerzone Good idea, but I don't have the time this week to create separate posts for this. Hopefully others can quote mine in their postings. Maybe I'll get to it later in the month. As for the LCAS+P thing, as far as I know it doesn't fix those issues. I had hoped that the "cancel" option would cancel you out of the taxi sequence, but I think it just closes the menu. The only way to fix these is to reslot (which has it's own issues, ED has said they're aware).

This one? The one that was last updated in June of 2021? Supercarrier Operations Guide I just looked in the core game files and found the updated guide (DCS World/Mods/Tech/Supercarrier/Doc for those looking), but it would help to also update the website, since people may not realize that that's where the Supercarrier manual is (I didn't and only looked on a hunch).

I'll give you this, it worked better than I thought it would on release. So credit where it's due. I doubt this was easy to figure out. Here is a track with traditional spawns with some of the issues from our squadron flight last night testing out the deck crew. I'll add more in follow up posts for more data as I continue to test this feature (which I want to work ). Operation Fly Swatter_WIPv1_3-20241204-205406.trk And here's a descriptive list of some problems we noticed: Stuck at "Waiting for ATC Status" message indefinitely. Occasionally resolved when there’s an available cat to taxi to and no obstructions, but this was not consistent. There's clearly some deck condition under the hood it's waiting for, but as a client you have no clue what that is and have no way to bail out of the sequence or force the next step. A busy deck frequently created gridlock. In one situation, we had guys get taxi’d to cats 3 and 4 and because the cat 4 guy showed up first, it wouldn’t taxi the cat 3 guy to the shuttle BUT it also wouldn’t launch the cat 4 guy until the cat 3 guy had launched. Stalemate requiring respawn. AI vs Client taxiing. It usually prefers the AI to a Client and so clients typically wait until all the AI are launched before they get to Taxi, BUT the AI frequently won't taxi if there's an obstruction somewhere (like another AI plane or a client, even a parked and spotted client). This required respawns for the clients to get the AI to GTFO. Lack of documentation. The changelog said it would be updated, but I have not been able to find it by searching manually on the DCS website or using a search engine. (Thanks to @rob10's comment I checked the game files and, sure enough, there's the doc. See comment below. Still not easy to find though. Please update the website ED! Thanks!) IFLOLS no longer functional without the overlay. It appears the lights are facing the wrong way, see: The boat is launching flares as client planes cross the fantail (wave off flares I believe but regardless of glideslope AOA etc., happens every time). This is annoying and distracting and I have no idea why it’s happening. I thought it was just a me thing, but then my squadron guys thought we were trolling them, so it's clearly not. Annoyances that it would be nice to resolve: Plane directors will taxi you across foul lines regardless of planes in the pattern or on final. I imagine it would be complicated (and probably cause more breaks) to add logic to prevent this, but that means you have to ignore taxi instructions sometimes because it always tries to spot you on the fantail first. Fortunately, it doesn’t break things to ignore the director and not cross the foul line, it will still pass you to the next director as long as you are generally going the right way. I'd argue that they should probably be spotting us on the bow for a recovery cycle, but I imagine that would create all sorts of problems for the way the deck is currently handled, so I guess I can live with the patio spotting priority. As long as I'm here though, could the parking menu have an option added to select where your plane will be spotted (e.g. 1)patio/el3/junkard; 2)El2/Corral/El3; 3)Sixpack; 4)Bow, etc.)? If we could have the menu come up once you clear the LA (see bullet below about ICQ), you could select your spotting location and avoid some of the traffic jams that always spotting on the patio first creates. There’s a new taxi speed restriction on deck that is enforced by jerking your plane to a halt (feels like grabbing a wire) and making you start again. This was obliquely mentioned by Wags in his video, but is not in any documentation that I've seen yet. W/o any way to tell what your taxi speed is tho, this gets frustrating. There is a way to turn this off in the special options, but I toggled mine off and it still did it There was a lot of complaining after Wags's video about how slow it would be to clear the LA. Ignoring plane director instructions is the way to clear the LA quickly. This is NOT ideal, but it works. Turn and get out, then obey the instructions and it eventually works out. Usually you have to get within a certain distance of the plane director for things to move along, but they will. REQUEST: Can logic be added so that when you get close enough to a particular director it will pass to him automatically? There are 3 near the LA and it creates problems to require you to Taxi close to the guy near the Cat 2 JBD to get the sequence to start (e.g. the plane landing behind you with proper spacing will probably be exiting the LA behind you and then you'll be required to turn around into him to Taxi back to the patio. Again, patio spotting is not my preference, but I'll deal with it.) You can only rearm with the jet cold and dark. No more hot rearms (at least from startup; after landing and re-spotting you can through the new “parking menu”). This is not clarified in any documentation I have seen. The new parking menu is key to interacting with this deck crew feature but none of the marketing or Wags’s video mentions it (don’t know about the DCS guide, but see bullet above). You pop this up with LCtrl+LShift+LAlt+P and it is the only way to get unstuck if something gets out of whack in the taxi sequence (that or respawning) Deck crew must be disabled to do ICQ or any immediate relaunch. It ALWAYS taxis you to the patio (or the closest open spot) and only then can you relaunch (and usually from a waist cat because you are closest to those). This makes ICQ--which is a series of traps and immediate relaunches--not possible with the new deck crew. That's fine, and we can turn the deck crew off, but it would be nice to have that parking menu come up right after you clear the LA so you can relaunch right then instead of taxiing to parking (especially to avoid using waist cats, which would block the LA and prevent recoveries). Perhaps there's already logic to prevent using a waist cat if someone has received a Charlie call from Tower? Will need to test... A "force next step" or "reset" or some such option either in the F10 menu or this new parking menu would be nice. If things get stuck, there's no way to unstick them short of completely respawning or restarting the mission.

Confirming that this has been my experience since yesterday's patch as well. I've added a few trackfiles for reference (links to OneDrive b/c files too large for upload). Also note, the ship is launching flares when client A/C are on final about to cross the fantail. Everyone in our squadron thought we were trolling them. "Nope, not us guys!" TSTA_1.4.3_CASE_I-20241204-170609.trk TSTA_1.4.3_CASE_I-20241204-205130.trk "Hornet Clara"

My 2 cents: Previous version dots = much too big (by roughly a factor of 4x). Current version dots = better but still too big (maybe a factor of 2x for me). Size of the dot at a distance is tricky, but close in it is most noticeable when the low LOD model gets overlaid with the dot and obscures the aircraft so that things like aspect and planform cannot be picked out. This happens less but still happens in the current version. I'd say around 3NM, but have not done careful testing. I do not see dots outside of about 15NM unless I use VR punch zoom. I can live with this. Not ideal, but manageable (for me). I understand the amount of variables that are being juggled here and that a lot depends on user hardware and settings (esp. resolution per eye for VR). So, while I don't agree with the angry tone, I do agree with those who would like the option to just turn the dots off (or, barring that, decrease size to 1 pixel). My settings: (see attached screenshots, NOTE: running my headset at native resolution, 2160x2160 per eye) My hardware: HMD: Reverb G2, 90hz GPU: 4080 (ASUS TUF) CPU: i7-13700K 3.4Ghz RAM: 64GB (2x32 DDR 5)

Very helpful! Thank you both @SkateZilla and @Megalax. Would not have found this on my own.

Since this arg was removed, I've been looking everywhere for a way to still get an old helmet for our squadron livery. Anyone found a way? I know from this thread: that some of the bort numbers are now controlled by country. Could that also be what's controlling the helmet?

SOLVED (will update OP): I hope this helps someone else. I was really pulling my hair out. The solution for me was to use MSIAfterburner to undervolt the GPU to 90% power usage (or more, your mileage may vary, but I started really low and stress-tested my way up). I found this solution by scouring this Reddit thread from 2 yrs ago, right around when the 40series launched: TLDR: It turns out this is a semi-common problem with NVidia 40series GPUs (regardless of manufacturer, but tends to be 4090, 4080, and in one instance on this thread a 4070) and has something to do with them trying to draw too much power causing a failsafe low power mode to engage that shuts off the displays. Some people were able to address this by replacing a faulty 12v cable, but I did that (even bought a newer beefier PSU) and still got blackscreens in bad weather. So far, the only thing that has affected it has been undervolting the GPU. I can fly in the rain now! Yay! (And thanks for all those suggestions @The_Nephilim. They actually led me to this Reddit thread, where I found the solution...after trying basically everything else under the sun.)

@The_Nephilim 1.) PSU is 6 months old, I'm not sure how many 12v rails it has. Do you know how I would find out? (It has 5 8-pin PCIe output sockets) 2.) Sort of, GPU is new to me (I bought it aftermarket from Jawa.gg, their official account). It was listed as new and came with original packaging. It did not come with it's 12pin cable. I ordered an OM nVidia cable from Ebay. 3.) Yes, I used DDU to uninstall and reinstall the nVidia driers when I installed the GPU. I also removed all previous drivers using DDU and then after that installed the fresh graphics driver. 4.) I think the black screen happens when the rain hits me, yes, but I'm not completely sure (see additional info below for non-rain-related event). As I said in the OP, during a flight with rain showers around me it was fine, but it was when I flew through the rain shower that it black screened. I have tried turning rain droplets off in setting but that has not solved it. I'll try a slow repair soon when I have the time. 5.) I do use a variety of mods and use a mod manager. I will also try turning them all off (uninstalling) and see if that affects anything. Additional Info: (Blackscreen without any rain) I was curious how everything would perform in 2D at 4k so I tried it about 2 weeks ago. I pushed all settings to max just to see what that would do to performance. I was on a discord call with a friend at the time and uploaded a replay of a recent flight. I set the camera on the ramp and padlocked to my jet. Performance was fairly good until takeoff when my aircraft went behind another aircraft momentarily. It blackscreened. This is the only other instance besides rain that has caused this behavior. Of note, I was still able to talk to my friend via discord until I chose to force a restart of my PC because I could not see to do anything. I didn't save the log or the trackfile, sadly, because this was the first time this happened and I thought I'd just pushed the graphics settings too far. Again, thanks!

1.) Corsair 850x PSU 2.) 90Hz 3.) Yeah, sorry about the Trackfile, guess that's not helpful. The mission only lasted about 4 seconds after getting in a jet in the rain and I made no inputs beyond looking to my left. I took a video on my phone, but was watching my hardware monitor numbers. 4.) Yes, those are eCores that I have parked (DCS only) using Process Lasso (CPU= i7-13700K 3.4Ghz) Thanks for the help!

***************************************************************** SOLVED: I hope this helps someone else. I was really pulling my hair out. THIS IS NOT A DCS ISSUE. IT IS A GPU (and probably NVidia) ISSUE. The solution for me was to use MSIAfterburner to undervolt the GPU to 90% power usage (or more, your mileage may vary, but I started really low and stress-tested my way up). See my final post below. ***************************************************************** I fly in VR with a Reverb G2 headset (full specs in dxDiag attached). I recently purchased an ASUS TUF RTX 4080 and have been trying to find the sweet spot for VR performance. Because it's nearly top end kit, the card has handled almost everything I've thrown at it...except rain. Apparently, it hates rain. Any mission with rain coming down on the client aircraft causes all displays to go completely black, not just the headset but the mirrored 2D display as well. I would say it's a CTD, but I can't tell if we're back at the desktop or not because the display is off. The PC is still running, but I can't manipulate the GUI without a display, so I am forced to reboot. What's weird is that the card has handled low level flying through dense urban areas on a relatively poor-performing terrain (Marianas over Guam) while maintaining around 40fps (see settings photos attached below). But in a fairly empty mission when it's rainy, I get almost immediate black screen upon loading into a jet (track file attached). On another test, I cold-started a warbird on Marianas in bad weather, but the field was clear. I started and took off just fine, but flew through a rain cloud just off the runway. Immediately black screen on all displays. (I don't have a trackfile, but can easily reproduce on request). These symptoms lead me to believe that the PSU might be shutting off power to my GPU and so this may not be directly DCS-related (only indirectly because the sim is asking for more power than the PSU is willing to give...at least on my current theory). Either way, I thought this might be something ED devs would be interested in and I hoped that maybe some intelligent forum-goer might be able to confirm my theory or set me straight. Is it my PSU or some rain-related setting in DCS? Thanks! Attachments: -DxDiag -4x logs from black screen events logged 9-2-2024 -trackfile for most recent crash event 9-2-2024 15:59:56 EDT -screenshots of NVidia Control Panel settings -screenshots of usual settings from launcher (DCS_1.png, DCS_2.png, DCS_3.png) -screenshots of lower settings attempting to find threshold of black screen events (Progress_stillcrashes1 and Progress_stillcrashes2.png) dcs_9-2-2024_183552crash.log dcs_9-2-2024_153230crash.log dcs_9-2-2024_155956crash.log LastMissionTrack.trk DxDiag.txt dcs_9-2-2024_151900crash.log

Thanks for posting @MoleUK These two videos are good examples of the pop in/out depending on viewing angle, which seems to me to be a slightly different issue than dot size but definitely needs addressing. As for dot size, I play on a potato PC (by DCS standards at least, see my signature if ur curious) and the dots are massive until about 3NM out and then, poof! I'd love to have a better PC and run crazy settings, but that's not going to be a reality for me in the near future. Whatever solution/adjustment is made, please don't discount us low-budget/low-end folks. We're not down here because we want to be. Thanks!