AstonMartinDBS

Sadly verify and restarting the steam client didn't solve the problem. Here's my log (standard OB/non-MT): dcs.log

Same problem here. Obviously I only get the low-res-textures at the Normandy map. I've upgraded from Normandy 1944 and The Channel to Normandy 2.0 for EUR 9,30 via Steam.

If you own both maps, you should see 3 offers at Steam: null EUR 9,30 (if you own both, Normandy 1944 & The Channel) EUR 13,96 (if you own either Normandy 1944 or The Channel) EUR 43,81 (full prize, if you don't own Normandy 1944 or The Channel)

I'm glad you were able to solve the problem! Thanks for your feedback and for sharing the detailled solution.

Thanks a lot, @cfrag! Your solution works great, and the mission file stays tiny compared to MOOSE!

Thanks for clarification @Chump. I'm just asking, why ED doesn't add the commands 'Transmit Message' and 'Set Frequency' to the advanced waypoint actions of ships? This it is already possible for ground units and makes it very easy to setup a well working beacon for such units, even if they are moving.

I've downloaded the latest version of MOOSE from github.com and updated the mission, but the problem persists. Is there any possibility to link the beacon to the moving Tarawa?

Many thanks for your detailled instructions, but homing to the beacon leads exactly to the initial point of my moving Tarawa instead to its current position. For testing purposes I've added a static Arleigh Burke right next to the movin' Tarawa and the origin of the beacon signal stays unchanged near the Arleigh Burke. Mission: CA UH-1H MovingFMHomingMOOSE.miz Track: CA UH-1H MovingFMHomingMOOSE3.trk Did I miss something in the script or in the mission setup, is there another issue or is this type of beacon for non-moving units only?

I've tried to setup a simple mission with a trigger which creates a radio transmission for a moving zone. Sadly it didn't work, because the signal doesn't lead to the center of the moving zone but somewhere (tested with both the standard open beta and the MT version of DCS). Feel free to modify my attached mission. Maybe you find a solution. For testing purposes I've added also a static zone. The homing to this static signal works without issues. CA UH-1H MovingFMHoming.miz

If you want to replace your stable version of DCS with the open beta on Steam: open the Steam libary right-click on "DCS World Steam Edition" properties Betas select "openbeta - Public beta versions"* *depending on your purchased DCS content (maps, planes, tech) the download of up to several hundred GB data starts immediately when you change this selection If you have the DCS World Steam Edition you'll find all configs, logs, etc. under %USERPROFILE%\Saved Games\DCS\ in both stable and open beta. open the Steam libary right-click on "DCS World Steam Edition" local data verify

Maybe this helps: deactivate VSync in the DCS options and set "Vertical Synchronisation" in the nVidia Control panel to "Fast":

Does this happen in every instant action mission for the A-4E or only in a particular one? Maybe you can recover your autosaved track from %USERPROFILE%\AppData\Local\Temp\DCS\LastMissionTrack.trk right after the crash. This may helps to reproduce the issue. As the A-4E is a mod and not supported by ED you should report that issue in the mod community forum:

Did you try to adjust the curves in the TrackIR configuration panel? If you wish, you can try my profile, which was originally from @Spudknocker: DCS World.zip Extract the content of the .zip file to %USERPROFILE%\AppData\Roaming\NaturalPoint\TrackIR 5\Profiles and select the profile "DCS World" from your TrackIR configuration panel. You may have to restart the TrackIR software to see the profile.

The heavy fog is still present at the landing area in the current OB. It's nearly impossible to find the runway without cheating (using F10 map).

You're right: there are currently two training missions for the A-10C II which are populated with the A-10C: "Aircraft Start-up" "Landing" All other training missions take place in an A-10C II.

The mirrors in the A-10C II are working fine on my system with MT: Try to clear the folders fxo and metashaders2 in %USERPROFILE%\Saved Games\DCS\ and run a slow repair (DCS Standalone) or verify (Steam). If this doesn't help create a report in the native forum for MT related bugs and provide a short track and your dcs.log file.

Not necessary - I've already opened a bug report in the MT bug forum, which leads to this thread.

I did some testing: It seems that the TGP rendering in the HMCS is totally messed up - but only in the MT version of DCS. MT: CCD MT: WHOT MT: BHOT dcs.log CA A-10C-II HMCS TGP CCD-WHOT-BHOT 3.trk

Did you also try to adjust the brightness of the whole HMCS by pressing DMS up/down short (while HMCS is SOI)?

The repeatet text is still present in the current OB (2.8.3.37854.1)

Thank you so much, it works!!!

Steps to reproduce: Correct behaviour: press WPN to open Weapon page press T2 (ASE) to open ASE page press T2 (ASE) to close ASE page/return to Weapon page (Probably) wrong behaviour: press WPN to open Weapon page press T2 (ASE) to open ASE page press R1 (AUTOPAGE) to open the AUTOPAGE submenu press R1, R2, R3 or R4 to select any option pressing T2 (ASE) re-opens the AUTOPAGE submenu instead closing ASE page/returning to Weapon page This behavior occurs in both the pilot's seat and the CP/G seat. There is also no difference between the MT and ST version of DCS. CA AH-64D ASE WrongButtonLogic.trk

I've changed the start option for the DCS World Steam Edition to "Play MT Preview" and activated "Always use this option". This works well, as long as I start DCS via Steam. But sadly every other way of starting DCS results in launching the ST version of DCS, i. e. via desktop shortcut (which opens the link steam://rungameid/223750) or even directly by executing the bin-mt\dcs.exe. Is there any way to start the MT version of DCS via a desktop shortcut?

Thanks for the hint, you've been right! I usually start DCS via desktop shortcut, which always loads the ST version of DCS.exe. At least now I found out that I have to start DCS via Steam to start the MT version. I ran your track again under MT and had the same issue. Exactly! Decreasing gain level to 2 made the bricks visible, but this is only a workaround.