Lasko

Figured it out, it defaults to XFER PROG instead of XFER WPN. I have it now click PB9 after going to EDIT MSN, and it loads all three target coordinates to L1-L3. I should have new Waypoint Editor release out today or tomorrow after a bit more testing.

I'm working on DCS Waypoint Editor mission support for F15E JDAMs using WPN MEM. For stations L1-L3 and R1-R3, coordinates entered for any of the three on L or R get duplicated to the other two. In the track file I enter coordinates for L1 and L2, and the end result is the coordinates for L2 are on weapons L1 L2 and L3. This seems like it must be a bug, but if not it makes the CFT stations much less useful. 2023-11-12 F15E L1L2L3.trk

Flat shadows causes other problems, including a mirror effect on some surfaces and sun angles. I'm just going to enjoy leaving shadows set to Off for a while.

I think it is bigger than Mi8 though. I added a Huey to the same mission, and it has direct sunlight on the front panels so it is somewhat better. The parts that are in shadow are still too dark. And the overhead console is also far too dark, and you can use the flashlight trick there again. 2023-11-12 UH1 Shadow High.trk

Thanks for checking it out. I have not used Reshade and have only adjusted the Nvidia control panel a bit to make the terrain not washed out. This is was the main complaint I found in other threads: I can adjust the Gamma and Brightness higher in Nvidia control panel which kind of improves the instruments but puts a grainy haze overlay on everything. 2023-11-12 Mi8 Shadow High.trk 2023-11-12 Mi8 Shadow Off.trk options-High.lua For the copy I made of options.lua with shadow off, the only difference was ["shadows"] = 0 from ["shadows"] = 4.

Is there anything being done to fix the problems with shadows? Setting shadows to Low or High results in about the same display, the instruments are unreadable. I've resorted to using the flashlight during the day to read the heading or blade pitch, it's really ridiculous. Setting shadows to Off seems to be the only workable solution. There are threads on this going back years, and at one time there was a shader mod that maybe addressed some of this but no longer works. Shadow Low/High: Shadow Off:

I noticed something on the F10 map fly by me today that looked like a cruise missile labeled MM-06. From Tacview I traced it to a GB-6. I found it again 90 minutes later and it was still going above 120,000 feet. This happens near the middle of the map, just south of Krasnodar. Tacview-20231104-083555-MM-06.zip.acmi

Here is Tacview from one that happened yesterday. For this one only about 1/2 the units were destroyed but the sequence seems typical. Tacview-20231029-205632-DCS-Georgia At War v3-clip.zip.acmi

This is what I've been missing. I saw something about 2.2 being the recommended setting, but after changing it to 2.0 it is much better. It could definitely go lower I feel too. And reshade sounds even better when I get some time to set it up properly. Thanks again for the suggestions. ETA: I stumbled across this thread too that had good suggestions. Tweaking the Nvidia control panel to Brightness, Contrast and Vibrance 60, along with gamma 0.95 made a huge difference.

Thanks, I'll try both of those. It has been increasingly frustrating since 2.8. I finally figured out to fix the light-switch brightness issue by running MT, and wasn't sure about playing around with gamma. Definitely worth a shot.

Can someone suggest what I'm doing wrong to have the glare and haze effects be so bad? I understand the idea of trying to adjust the effects for direction, sun ,etc. but now it feels like 1/2 the time I am flying blind in the fog. Now with the added dust effects it is almost impossible to operate near the ground facing anywhere near the sun. I fly real airplanes all the time in the daylight and am never blinded to the point that I can't see clouds and terrain. This seems like I either have something set wrong, or is just so broken that I can't even fathom. Appreciate any suggestions. null

I was able to fix it by changing these two options: Broken: ["AA"] = "DLAA", ["Upscaling"] = "DLSS", Working: ["AA"] = "MSAA", ["Upscaling"] = "OFF",

I wasn't sure where this should even be reported, and just noticed this today. I don't think it was doing this the past few days, and I've changed settings so many times this week I couldn't say what triggered it to start. It looks like bad video recording but this is exactly what it looked like, with the sweep line being broken and ghost trails following along behind it. 2023-10-24_14-49-39.mp4

Agree, the dust effect is way overdone. Every helicopter landing is like in a dust storm with zero vis. This needs to be adjusted down or an option to disable.

Here are the start/end points: WP1: 44°42'19.16"N 39°34'15.99"E | 361ft WP2: 44°42'48.74"N 39°34'21.14"E | 367ft I did see on one replay attempt there were no red units visible on F10 so I restarted DCS and they came back. I can see the Abrams sink below ground level in F7 view. I even did it differently this time by clicking the unit on the F10 map then clicking the control icon to exit, thinking that exiting through the menu somehow contributed.

I just did it again on Caucasus Georgia at War. It happens after 19 minutes, 23:48 time stamp. Georgia At War v3.0.24_evening-20231021-195520.trk

This happens all the time on the Hoggit servers. I exported the server Tacview into Excel from one about a year ago. At 6 seconds it recorded 773 HasEnteredTheArea events, then 11 seconds later 711 HasBeenDestroyed events. I don't think a client track or Tacview will help because by the time you connect it has already happened.

I managed to do it just now, it took about 10-15 tries but the Abrams sank below ground level then exploded when I tried to control it again. Hope this helps. Persian Gulf At War 1.0.0_morning-20231004-134355.trk

OK, that wasn't exactly true, I do have the track file but it is 88MB. If it will help, I can try to reproduce it at the beginning of an MP track which should be fairly small.

Here is something I've run into from time to time, only on multi-player. I wasn't even sure how to describe this and haven't found anything by searching. Re-create steps: 1. Stop the vehicle on a dirt area. I don't recall it ever happening on pavement. 2. Open the menu with ESC, choose "Select Role" 3. Close the role screen with ESC, you are left in the JTAC slot. 4. Change to F7 view. 4. Vehicle sinks into the ground. If you attempt to control it again, it explodes. If you exit the server and rejoin, it will be back on the surface. I don't know if other players see it buried, but suspect not. Sorry for no track, I've never been able to cause it in a single player setting. 2023-09-30_16-24-36.mp4

Agree, the cockpit display issue can be fixed by changing the shadow setting. I set it to "flat only" a long time ago before changing hardware, but also never had the unreadable issues until recently. The terrain brightness issues started around the same time, so I tied them together.

Here's an example from the A10C landing lesson. "Press the Space bar key to proceed when the radio is tuned to 131.000" Right.... null

The only thing I can offer is that I have encountered this also and don't know how to cause it. My setup is super simple with an RTX 3070 and one monitor displaying DCS and the second monitor displaying Chrome, Discord, etc. I just played about 3 hours on a PGAW night mission and it didn't happen at all. My feeling is it must be related to the brightness problem when switching views, like F11 back to F1, but what triggers it when not switching views I have no idea.

This is a big problem that needs more attention. I was doing the A-10C training missions yesterday and the cockpit radios and other instruments are unreadable without moving the view position fully forward or back, and the HUD is completely unreadable in many of the lessons from the "haze" in the sky. I've also noticed this in some of the Ka-50 training and IA missions, the cockpit instruments are completely opaque so that you can't read the channel number on the R828, for example.

DCS Aircraft Command Entry This is a utility to build command sequences for DCS aircraft, which are then sent as DCS-BIOS commands. DCS-BIOS supports nearly every switch and knob in DCS aircraft. Selecting an aircraft type builds a list of all commands for that aircraft, along with the range of values corresponding to the possible settings. Commands are added to a profile with the selected setting, and the command sequence is sent to the aircraft by clicking a button or via hotkey. Profiles are stored in a database and can be shared between users via a text string or JSON file. Aircraft supported in the initial release: A-10C AH-64D F-15E F-16C F/A-18C Ka-50 Mi-8MT UH-1H F-15E support requires updated DCS-BIOS files not available in a release yet, but they can be downloaded from Github. Support for all DCS-BIOS aircraft will be added. Release information and more complete instructions are available on the Github project page: https://github.com/atcz/DCSAircraftCommandEntry Thanks @Epiic_Penguin for inspiring me to move this project forward into a working prototype.