ReMZero_kkrn

In openbeta 2.8.4.38947 The only impact so far is a traceback in the log file (line 485). It's not happening now, but at one point there was a crash that I believe was caused by this. According to the logs, it looks like you tried to call an ATC that doesn't exist and failed. I think the solution is not to land on static object carriers... dcs.log

Although there is no conclusive evidence, this phenomenon can occur when a ship-based missile or ground-based SAM loses its guidance target for some reason immediately after launch. (e.g., shot down by another missile). ... However, it seems to no longer occur in DCS2.8.4.38947? (Experimented with Tico 20, Pyotr 20, Target 84...) If you lose sight of the target, it will self-destruct, but at least it will not be stationary right above the VLS. P.S. I think the Arleigh Burke mapclasskey is closer to P91000069 (NATO icon DD) rather than P91000067 (NATO icon CC) in terms of ship type....

With the game not running, "./username/Saved Games/DCS.openbeta/Config/options.lua" file, You can change it manually by changing the ["width"] and ["height"] values under ["graphics"] with something like notepad. Sets the display resolution lower than the display and he starts DCS, it will start at the specified resolution (window size). For example, ["width"] = 1280, ["height"] = 720, You can also set ["fullScreen"] = false if you prefer. When you start it, just change the resolution to your liking from the settings as usual. By the way, Rename or delete the configuration file, it should start with the initial setting (I think it was full screen)

The ACP label is written in A-10A-CPT-TEXTURES/A-10A_Devices_02, and it seems that it can be fixed by changing the order. (Reference: TO-1A-10A-34-1-1 (May 3, 1999) Page. 1-54) However, smokepods etc. do not appear as "SMOKE" (arg_value 0.14?) and HDGP seems to be defined as LDGP. By the way, GBU-10 and GBU-12 are displayed as E/O. As an aside, I feel that the notation of NMSP is also different, but which lot is it based on...? (Reference: T.O 1A-10A-1 (20 February 1983) Page 1.81) NMSP doesn't work on FC3 aircraft, so it's just a matter of looks.

The Yak-52 and P-51D Lua files have an entry "date_of_introduction" that appears to indicate the year of introduction, but at least it doesn't seem to work in the mission editor... Notation method seems to be " Introduction date = YYYY.MM, "