Lasko

I ran this some more to get good track files. In this first version I used TOO mode with a mission file waypoint. Three of the missiles turn and crash, one reaches the target. The same altitude and speed issues happened again. There are also issues with the engine run time. All are dropped within 15 seconds, but the engines appear to burn out after a fixed distance so the slower missiles run longer. Also when the engine stops the entire vapor trail disappears. Tacview-20231211-172742-DCS-F18 AGM84E.zip.acmi 2023-12-11 F18 AGM84E TOO PG.trk In this file I manually programmed the coordinates for PP mode. Two of the missiles turn and crash at nearly the same point as the previous file and two reach the target. In this file the DL linked missile made it to the target but nothing was displayed on the DL image until a few seconds before it hit. This never used to happen either. Tacview-20231211-175230-DCS-F18 AGM84E.zip.acmi 2023-12-11 F18 AGM84E PP PG.trk

There are still problems with AGM-84E cruise missiles, although better than flying in circles. I launched 4 SLMR with PP coordinates from 37,000 and FLT HIGH. 3 out of 4 hit the target, but the flight profiles were random. Before the recent changes they would fly at 35,000 when set to high with matching speeds. Here is the summary of the four launched: #1 - STA8 - Flew at 362 M1.45. Eventually climbed to 400 and then crashed 30 miles from the target. #2 - STA2 - Flew at 348 M1.40. Reached target. #3 - STA7 - Flew at 339 M1.39. Reached target. #4 - STA3 - Flew at 333 M1.37. Reached target. To me it looks like two problems. The "small random trajectory spread" is too much. It won't be possible to time long distance strikes with the differences in altitude and speed. The first weapon should have reached the target with the other three and not crashed randomly. Tacview-20231211-153757-DCS-F18 AGM84E.zip.acmi

Not sure if this is a Ka50 problem or vehicle damage problem. The SA11 C2, TEL and SR are sometimes impossible to hit using HE rounds. Switching to AP does damage every time. In the track file I set up 6 SA11 vehicles. The first five are not damaged at all by HE bursts, and are destroyed by one AP burst. The last is destroyed by HE for some reason. 2023-12-02 Ka50 SA11.trk

I've only seen it happen when switching missions, and doesn't seem dependent at all on the number of clients. It's happened with 2 or 3 clients, or more than 20.

Thanks for adding spectator mode. I didn't expect you to also build it into the UI, but that's even better. Great work!

Here is Tacview of one that happened yesterday. I was only looking at units destroyed before, but in this one the units destroyed coincides with the first spawn of AI aircraft. I'll have to look at some of the other examples to see if that is a common thread. This is kind of game breaking, and I wonder if this is happening often on MP servers and is just being ignored? Tacview-20231122-205125.zip.acmi Tacview-20231122-205125.pdf

This has been driving me crazy, why it will sometimes enter the frequency and other times not. Here is a simple track, radio #2 comes up with 133.000 and I enter 249.500 which is accepted and 133.000 is displayed in the entry line. Clicking enter again to put 133.000 back doesn't work and 133.000 just flashes. 249.500 can be put back in radio 2 but not 133.000. 2023-11-19 F15E Radio Freq.trk

Version 1.3.3 is released. v1.3.3 Feature Changes: F-15E: Added Smart Weapon mission coordinate entry. DCS-BIOS version update to v0.7.49. Added the ability to install DCS-BIOS daily Beta builds. The Beta builds may not be fully compatible, for example the definition of F-15E UFC keys 0 and 7 is changed in the Beta version and will not function. Bug Fixes: F/A-18C: PP mission displayed with an X when the elevation is set to zero.

Every time you select SMRT WPNS from menu 2 the station selected with the vertical bars switches to the next in order. If you have station 2 selected, then use M, M2, SMRT WPNS, station L1 is now selected. This continues in order through all stations.

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