Insonia

Steam use ST by default. User must select launch option

Make sure your friend and server are on the same version. Mismatching game versions can result in "server offline" errors. Let's assume you've completed every step correctly. then Please verify that your router's WAN IPv4 is public address. public IPv4 address is required for hosting server via IPv4. Carrier-grade NAT or any upfront NAT is unable to host any server. If you don't have a usable IPv4 address but do have IPv6, make sure your machine and clients (friends) have IPv6 enabled and working properly.( Remember creating an IPv6 firewall rule at your router to allow 10308 traffic to your server. Port forwarding is not needed for IPv6.)

show_param_handles_list() net.dostring_in('export','show_param_handles_list()') -- In mission editor or GUI In addition to list_cockpit_params(), this cockpit params UI function is also available in export environments and somehow hasn't been documented or talked in the forum. Hope ED won't remove this. To access this UI function from the mission editor, use net.dostring_in('export','show_param_handles_list()'). The names of cockpit params and how they change were shown in the values and graphs. Hope this will help you when making cockpit triggers.

show_param_handles_list() This function is available in the export and server environments. All the params and how they change the values were displayed in value and graphics. Hope ED wont remove it someday.

In a constant-speed prop system. Increase throttle with low RPM setting, which increases MP and BMEP(Brake mean effective pressure). At a low attitude, the air and oxygen are abundant. Just like your piston engine car. If you put too much air and fuel into the chamber per stroke, detonation , boom. your engine trashed. Increased RPM via prop handle reduces MP and BMEP pressure. It allows you to deliver needed power spread over more cycles. reducing the risk of detonation. The risk of *excess RPM is heat and wear. High RPM increases friction coefficient, fuel burn, and both increase temperature. has a risk of pre-ignition. as long as your cooling is okay and you do not excessively abuse it for too long. You can get away with it. When it gets too hot, pre-ignition and even detonation happen as well.

because you mentioning you have mod issue. Try rename your Saved Games\DCS folder, restart the game generate a clean configuration. if it's working reinstall the mods and move your input profile back. If you or steam accidently forget some of your DLCs. Steam Support :: Find Downloadable Content (DLC) for My Games (steampowered.com) Go to the DLC tab and make sure your DLC is enabled. If you want cleanup the DCS install in steam: use the backup and restore feature. "Move" feature will move everything, including extra files you add into installation. did not check if they were valid. "verify" feature did not care addition files you add to the game. "steam backup" feature: Steam Support :: Using the Steam Backup Feature (steampowered.com) "backup" only packs and restores the "vanilla" files. backup the game, delete remaining files, the restore. you have the clean install.

D:\Steam\steamapps\common\DCS A-10C Warthog\ C:\Users\bugfishtm\Saved Games\DCS Warthog\ It's a legacy "Digital Combat Simulator: A-10C Warthog" from 2012. Depot 61012 (Digital Combat Simulator: A-10C Warthog english) · SteamDB Support might dropped. and I doubt many people still remember those logs or do anything about it. Follow the steps to repair the game: Steam Support :: Verify Integrity of Game Files (steampowered.com) delete C:\Users\bugfishtm\Saved Games\DCS Warthog\ There is time period in the past allow player transfer their old "Digital Combat Simulator: A-10C Warthog" to "DCS World". If you never did that. try contacting the ED support team and asking them nicely whether they can give you a new A-10C license or discount so you can play it on "DCS world" Many old games share the same fate. Have a difficult time running on a modern system. if you insist on playing retro versions of games. Try to find and play it on an old machine with old hardware and drivers for best compatibility.

In DCS, your input profile is saved as DeviceName{DeviceGuid}.diff.lua As long as your device's GUID matches, the game will recognize it. GUIDs are pseudo-randomly generated via a seed that is only unique to each Windows installation. Moving to a new system or reimaging Windows creates fresh seeds and GUIDs. You must rename or reimport the profile. There is a quicker way for doing this. Any program or cmd/powershell script that does a "batch rename" which searches all files and replace the old GUID with the new GUID at once. If you have never learned such things before, it may not be worth the hassle only for this. Simply rename or re-import your profile manually.

GIS software and lots of manual work as well. flappie has some work done and how he does it. DCS F10 map use UTM projection.

it's Chinese new year. Everybody stop working *gradually(abruptly) from February.

the file is corrupted. Check if you can unzip the content. Please try reupload next time you crash the game.

No, just 8 bits of "depth" per color. The Desktop Window Manager (DWM) restricted windowed apps to output content at only 8 bits per color channel, even if the display supported a higher bit depth. To output 10 bpc/30bits , the software must use specific APIs (directX games also must work under exclusive fullscreen) and is very difficult to implement because the Windows color system is a total disaster. Aside from production software like PS, almost no sane person bothers to support such things. Only 1 game I know natively supports 10 bpc is alien isolation. It can never fundamentally resolve the banding problem. Those are "working around" solutions through shaders and artistic "tricks," called "dithering," an optical illusion that breaks up the posterization and blends them together. IT just "hacks" that worked well enough. but both(provide 10bpc support or good dithering algorithm) required efforts that they probably do not really want to.

The tracks, settings are for the mission intro/cinemas. Snapview sometimes used for adjusting cinemas view. or the developer just forget.

This is not "evidence".. Did you have "fullscreen" checked before? By default. brand new DCS config disable the fullscreen setting. appSettings.lua was introduced probably as early as 2.8 or at the end of 2.7 release. DCS generates this file ONLY when it runs in window or borderless mode( uncheck the fullscreen in the settings) it use this file to remember POS in window mode instead of Windows shell "bags" registry.