Insonia

5.1 Remote Control For remote control, DCS servers use TCP port 8088 by default. This port has to be opened on the server's router for remote control to work. UPNP routers will open this port automatically (this feature is work in progress and currently does not always work reliably). For remote control of the DCS server, the control PC (or device) has to be logged in into your DCS account on the DCS homepage. NOTE: your PC and server should be logged in the same account! You can't control servers started from different DCS accounts (this feature is in development). In order to get control open your Profile page and select your server or visit URL: https://www.digitalcombatsimulator.com/en/personal/server/ (EN)

Steam use ST by default. User must select launch option

The sky shader issue might be dxvk bug. It happens on other compatible layer softwares as well in dcs. For many years. Only linux proton's dxvk is less buggy. The graphic is corrected only in proton in recent years. sometimes still crashes tho. But it's Linux stuff. Virtualization and compatible layer is beyond normal game dev's ability and interests. Report this to the compatible layer dev to improve their product.

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.

Inertia coupling goes along the inertia axis with smaller radius, thus making it spin super violently. F-100s inertia couple problem mostly happens at high speed and high attitude. Not takeoff and landing. its has nothing to do with it. Starting a rapid roll movement along with the "inertia axes" and "aerodynamic axes". the roll produces a rapid change in AOA. When the roll velocity surpasses the critical level. Aerodynamic forces can no longer hold it. It tends to roll along other axis. Another is torque-induced gyroscopic precession, only occurs when the aircraft pitches (lateral axis) or yaws (vertical axis) not roll, motion against the inertia axes. which causes the nose to slightly pitch diagonally. the swept wing is more sensitive to the angle of attack and angle of slip. Adverse yaw might be the dominant force tilting the aircraft in that accident. However, oscillating the nose will oscillate the Δβ can only deteriorate the situation. Btw , if you oscillate the nose up and DOWN in DCS ED modules. it rocks the nose diagonally, which raises my suspicion. But who knows, maybe their jet PFM API also share the same math with their warbirds..

I already cited this in my previous posts.The book about The coupling effect in aircraft.I mentioned at the beginning that some yaw to the wrong direction if it was the gyro effect alone. We still just don't know what's happening within the game. And probably they don't want to answer... Many coupling forces could be reduced and damped significantly in a well designed aircraft, lower spin mass , better aerodynamic stabilizer and control system. It's no longer a safety hazard. No longer impact the performance. But this is basic physics. it still there. It is measurable. Unrelated documents probably have no intention to cover this topic. I found few articles about earlier F-100 development you may want to look. We will have F-100 in the future, and I'm looking into it. Gyroscopic effect interacts with other coupling effect and lacks aerodynamic stability at low speed. can trap pilot into a hazard known as "saber dance" https://aviation.stackexchange.com/questions/31614/do-gyroscopic-forces-from-rotating-engines-significantly-affect-yaw-or-pitch

sorry. Previous post: I made a mistake and was misled (by Google, of course). Those M$ abbreviations were really confusing sometimes. I was brainfogged because there is similar name scheme and also involved in codecs. The correction: DirectX Graphics MMS( dxgmms1.sys dxgmms2.sys dxgkrnl.sys) is the driver controlling the VIDEO SCHEDULER(VidSch) and VIDEO MEMORY MANAGEMENT(VidMm). MMS may stand for memory management and scheduling in this instance. Microsoft media stream MMS and Directshow is legacy video encode/decode stuff, no longer used and not ring0. Modern Windows software like clipchamp and xbox gamebar use the Media Foundation Interfaces (IMF) and DXVA to provide encode/decode accelerations. Only drivers running at ring0 can trigger the BSOD. WDDM is ring0. Streaming libraries themselves at user level cant not directly crash the system. ===============================================/ An exception in VidSch functions triggers the "VIDEO_SCHEDULER_INTERNAL" BSOD. If it happens in VidMm triggers the "VIDEO_MEMORY_MANAGEMENT_INTERAL" . The cause is usually traced back to graphics drivers. If the windows and drivers are correctly installed, there is not much you can do about it..(single event, faulty driver or faulty hardware) The blackscreen you experienced is most likely a TDR event. Timeout detection and recovery (TDR) - Windows drivers | Microsoft Learn VidMm and VidSch manage the GPU schedules and memory. If for whatever reason, the GPU packets can't be sent to the GPU before reaching TDR . The VidSch (GPU scheduler) thinks the device is gone and needs to be reset. Kernal will try to restart it, and it will create the temporary screen flicker ( if recoverable). Or remain in backscreen (unrecoverable obviously). The Windows events/logs will add an entry about attempting to reset the graphic driver during each instance. However, if the graphic card/drivers crash the scheduler first, You receive this "VIDEO_SCHEDULER_INTERNAL" instead. And "TDRLevel" and "TDRdelay" in the registry control what the kernel should do and how long to wait before taking actions. You might already see people mentioning those 2 registry entries somewhere in the forum when there are dxgi_error_device_hung/removed and blackscreen errors. Changing those values might help few people who have laggy drivers or GPU. Most of time, they have some sort of fault in the graphics card. And the root of a BSOD or TDR event can be anything.. The clipchamp is not a necessary cause for everybody. For you, encoding or decoding video might just compete for GPU resources and put the GPU scheduler and GPU driver at work, and system just go "oops!". Hopefully, this is just a single event.

You can find windows BSOD memory dump at %SystemRoot%\Minidump. and C:\Windows\MEMORY.DMP DCS dump can be found in saved games\DCS and %localAppData%\DCS Generally, this particular BSOD is relate to graphic drivers. those are probably just coincidence, Single-event upset. If this issue continues. I would worry more about the drivers, windows, and hardware.

Yes. you must set your vertical resolution lower than your native resolution. Otherwise, DCS will run as borderless mode. DCS option menu, resolution setting allows you type any custom resolution. select the number then replace with any number you like. Your target height should be 1440-"windows taskbar height"-"windows title bar"

CHEATING You have the right roll input. despite this minor right roll input. Your F-16 also rocks to the left. just like people have already tested. always to the left, always. ←↑ So what is this coupling effect? Is this has something to do with engine gyroscopic precession?

ED allows the 3rd-party use what they called the EFM (external model) letting dev have the freedom to design their own mathematics. ED themselves use what they call PFM (professional flight model). probably all share the same mathematical foundations. im not saying they were correct in this game. I'm just saying IRL it just basic physics. it will have an effect on aircraft flight characteristics, only matter how much. Coupling Dynamics in Aircraft: A Historical Perspective PDF Download | FlipHTML5

"rolling" while pulling. or Is it yawing? and the rolling just side effect by slip stream and vstablizer torque? Angular torque IRL can be caused by on-aerodynamic forces like engine gyroscopic force coupling, GCs and aerodynamic factors like unequal disturbances and anomalies from increased AOA. It is unreasonable to expect zero direction changes while drastically changing pitch attitude and making no pilot corrections. However, what ED did with their math, we have no clue. It did not look like pure non-aerodynamic or aerodynamic. It did not have a dominant one-sided yaw or roll tendency during high AOA level flight. gyroscopic.. Some of them simply yaw/roll into the wrong direction...