adamant365

You aren't crazy, it was unreachable for me as well.

I have a similar issue. When running a mission on the OB Server, I can see friendly contacts on the SA page but the data block in the bottom right doesn't show callsign (e.g. SD11 for Springfield 11). When I run the same mission as single player, it works fine.

I don't know if this is helpful to you, but apparently others have had issues with the TDC slew. This is a youtube video I found: Granted, I don't have a Warthog throttle so this doesn't apply to me, but it looks like it got several other people back up and running.

Hey raus, I think this work is brilliant. It's exactly looking for for mission planning. However, I've run into an issue importing a .miz file. I've been trying out one of the DCE Manager dynamic campaigns, and I'm trying to load the first mission into Datacard Generator, but none of the data is imported. I've attached the .miz file I'm trying to open. I am able to open other .miz files from "simpler" missions just fine. Thank you for your hard work! EDIT: You can disregard this. After doing a little more research and unzipping the .miz, it appears as if the format used for these generated missions is either very old and/or different enough that it probably wouldn't be supported by your Datacard Generator. Crisis in PG-Warthog_first.miz

Okay, I figured it out. These changes will change all radio menus and submenus, the actual communication text between you and ATC, your wingman, etc., and the tutorial text. It's straight green which I think is a good compromise and is highly visible even against white clouds. Haven't tested much but it's a start. This is the end result: BACK UP ALL FILES YOU ARE GOING TO MODIFY BEFORE CHANGING THEM. I take no responsibility for breaking your game and this certainly wouldn't be supported by ED. I haven't done much testing as I just figured this out. I modified the following files: <DCS Install>\Scripts\Common: 'utils.lua' - added a line in the COLOR { section "GREEN = makeColor (0,255,0)": COLOR = { WHITE = makeColor(255, 255, 255), LIGHT_GRAY = makeColor(200, 200, 200), DARK_GRAY = makeColor(74, 74, 74), RED = makeColor(125, 75, 0), BLUE = makeColor(0, 75, 125), BLACK = makeColor(0, 0, 0), GREEN = makeColor(0, 255, 0) } *Make sure you insert a comma at the end of the BLACK line <DCS Install>\Scripts\UI 'GameMessages.dlg' - changed every line that was 0xffffffff -or- 0xf5f5f4ff -or- 0x000000ff to: 0x00ff00ff <DCS Install>\Scripts\UI\RadioCommandDialogPanel: 'CommandMenu.lua' - changed every line with WHITE to GREEN. Also changed every line that was 0xffffffff or 0x000000ff to: 0x00ff00ff 'RadioCommandDialogsPanel.lua' - changed every line with WHITE to: GREEN. 'CommandDialogsPanel.dlg' - changed every line with 0xffffffff or 0x000000ff to: 0x00ff00ff 'CommandDialog.lua' - changed every line with 0xffffffff or 0x000000ff to: 0x00ff00ff Finally, I saved copies of the modified files to a separate folder on my PC so I can potentially restore them after any updates. This works now but may not in the future. If you want a color other than straight green, you can find the hex code for that color on the web. Search for HTML CSS Color Online Color library. The 'ff' at the end appears to be constant in DCS. Only the first six digits after 0x need changing. And if you want a different text color for the ATC text, you can substitute all of my "GREEN" entries with whatever. The x,x,x number (0, 255, 0 for GREEN) is the RGB value, also available on the HTML color library. I know there's a way to include a background around the ATC menus because one of my tests I had accidentally made the whole thing a big green box. I don't remember which change though...

This is definitely possible, but I don't know which .lua files to edit. I was able to successfully change the heading color to green (where it says ARC-210) and some of the menu headers, but I wasn't able to change the actual contact list (Flight... ATC... etc.) or actions fully. I was able to change the "background" (shadow) to green, but the "foreground" main text color is still white. I probably changed 15 different 0xffffffff (white) values to 0x00ff00ff but the color is still basically a very light green because the main text is still white. Anyone know how to change the text color of the actual options within the radio submenus??

Major facepalm. I was looking through my nVidia control panel settings and noticed "Antialiasing - Gamma Correction" was globally set to On and I hadn't disabled it with my DCS-specific settings. Knowing AA gamma correction can cause excessive bloom, I turned it off for DCS and the annoying "glow" around my HUD symbology is gone. Now I can fly with my HUD at 100% brightness and it's just a brighter HUD and not all bloomy like before. It had been driving me nuts and it was as simple as an overlooked setting...

Yeah, I was simply thinking a little outside the box with that idea. I've been doing several practice missions and the HUD brightness is always at max so the first step for me is to turn it down by about 50%. If I start cold and dark, it's no problem. But surely there's a way to tune the bloom effect so that it isn't so pronounced. I have to think there's a way to do this by editing the "bloom.fx" file or some .lua file, but I wouldn't know where to start with that.

Hello All, I've tried searching several different ways and can't find anything. Is there a way to turn off or reduce the bloom effects in DCS? I'm not flying VR so the VR bloom setting has no effect. I have mostly been flying the F/A-18C and find the bloom a bit overdone. I have to turn down my HUD brightness when loading a mission to remove the bloom effect around the HUD symbology. I guess an alternate question would be, is it possible to set a default value for HUD brightness? I do like the bloom effect when viewing externally, but the effect on the cockpit displays, especially the HUD, is a bit distracting. Thanks in advance.

Whenever using the AG radar in MAP mode, if I SCS right to initiate FTT (with the AG radar on the right DDI), the display rapidly flashes between the map image and the track screen with the "brick." This occurs when initiating SCS right FTT from MAP or EXP 1, 2, or 3. The mode does switch to TRACK as indicated at the bottom of the radar display. I've attached a short track file that demonstrates this. Flashing AG Radar - SCS Track.trk