Insonia

it's obvious your "center" viewpoint aspect is 4480/1080

Those puny motors may not have enough torque to stop humans from exceeding the stop position before the loading cell has adequate force-sensing ranges. Using holding torque as a stop/lock draws maximum current, which is very impractical for long periods of use. while you are burning your motor and power supply out. Then the motor torque control will create a lot of jittery/spikes that you may able feel or bearly, but the load cells can measure and tell the difference. then you may have to apply a ( algorithm or hardware )filter to smooth the value., which can be quite ugly and inconsistent. A bolt mechanical lock or limit gimble range. should be simple and better

LOL. Sorry for off topic but dcs is flat. What you saw is shader tricks. Visual only.

The problem is that the "lua_state" is not associated with particular files. The "lua_state" is used and shared by all cockpit scripts during loading and execution. In this "lua_state", any script has the ability to change any other variables and functions. Where the script originated doesn't matter to lua_state. If there is ONE file, just one file that not protect by IC . You can run any code throughout this procedure and access all functions and tables as long as those scripts are in the same state. include overriding tables and functions, manipulating strings that originated from other files and hijacking the loading process. bypassing the IC completely. For example. A loadout.lua file inside of users/missioneditor folder, which is not protected by IC, and supposedly should only contain a loadout table. because this file and unit_db use the same lua_state. We modify this file and add our custom code. while loading it into the ME. All of the units, weapons, and sensors in the _G table(globe table), are accessible via this file. Imagine a user modifies the missile's speed to Mach 20 and range to 100 nm. ED must make the unit database readonly in order to prevent cheating. So they have to separate the "ControlsIndicator.lua" to a different "lua_state", which also requires them to modify the C++ part. Introduce extra work, and It's up to them to decide. But it is very unlikely they will make changes for those indicators.

his CPU only has 4 cores. And it's a fairly weak CPU. i5-4670K: https://www.intel.com/content/www/us/en/products/sku/75048/intel-core-i54670k-processor-6m-cache-up-to-3-80-ghz/specifications.html mask: 1111 means all 4 core is in use.. pretty normal.

the QR code and manual code are compatible with every program. It's using the standard TOTP algorithm (RFC 6238). Compatible with any 2FA program that supports RFC 6238, which means almost every 2FA program does. Google also use RFC 6238 by default, but you can choose not to use it.

I have had the smoothest experience since 2.9 (single player) on MT. You only got 4 cores and 16G ram, then you may not be affected by the bugs (like HT and core parking) which only affect higher-end systems. You do not need to have high CPU usage on the process to experience stuttering; a lag or stutter happens simply because a frame cannot arrive on time. There are many factors that slow down a process and not have very high CPU usage, like I/O, hardware/driver responsible times, etc.. So What is this stutter feels like? completely random? periodically? Or are they related to certain gaming events? what's your graphic memory usage, system memory usage when stutter happens. you mentioned have low CPU/GPU usage. when game overcommiting and exceeding graphic and system ram can create huge lag caused by the I/O ( indications like very high disk usage, inside of graphic cards may have very high memory "bus" usage ) if possible, maybe you can provide a video or something to demonstrate the issue And Windows also got dashost stutter issue,it only affect people with a bad designed product/driver and network smart devices. DCS also utilized some APIs related to the dashost and provid PnP features. Have you tried this: https://www.google.com/search?q=windows+dashost+stutter Or just submit a ticket to the support page https://www.digitalcombatsimulator.com/en/support/

The certificate is OK. It's for the *digitalcombatsimulator.com. not the dcs.world. Without "forum" prefix, the DNS name resolves to the main site(digitalcombatsimulator.com). Modern browsers prefer the TLS and completely ditch the http. DNS + http 80 redirect will not work. They should just use HTTPs redirect. An improper name resolver causes problem. Should be in this section https://forum.dcs.world/forum/61-forum-and-site-issues/

It depends on how the aircraft cockpit script defines their functions. LeCuvier has a guide for adding additional keybinds. You can add multiple input entries with different "value_down" or "value_up" on a single cockpit device( cockpit_device_id ) or different up/down icommand. Like Battery on and off for A-10 {down = 3006, cockpit_device_id = 1 , value_down = 1.0, name = _('Battery PowerON'), category = _('Electrical power control panel')}, {down = 3006, cockpit_device_id = 1 , value_down = 0.0, name = _('Battery PowerOFF'), category = _('Electrical power control panel')},

if you read the op. It's about a ML/DL cloud-based "AI" client joining as a client. Very specific type of implementation. You stretch the topic a little bit. There are a lot of misconceptions about AI in video games. They are actually designed to be BAD in a specific manner. good enough to be functional, but bad enough to be beatable. Todays AI can already annihilate most humans with ease in a game/simulator. But there is no fun if you can't win. And ML is no miracle to turn "AI" humanlike either. Dont get hyped just because they add ML/DL into their works. Company ofc gonna do whatever it takes to make their product more appealing and profitable. They are not stupid. They haven't done it or will not do it because the (cost of) technology didn't get their yet. and they may have a better place to spend their resources. The conventional "ai" follows scripted decision trees. The scale of the tree is limited by human factors, but it is easy to adjust and tweak. Fully under developer control. From multibillion-dollar triple A studios to indie developers, they all do in this way. ML-generated nodes are difficult to understand and tweak from a human perspective. Because the impracticality No game company and developer actively uses ML as their "AI". Instead, the industry treats ML as a statistical research tool, aiding their normal development circle, not a replacement for those features. Even the most advanced AI company struggles to turn profit, revenue and operation cost barely break even. Ed's CEO Nick said before in the interview that they are relying on pumping unfinished products to keep the cash flow; otherwise, there will be no DCS. If he spends a million on something, it better have a return and be profitable. And it's not. There are many commercial level "AI" can enhance current DCS gameplay already. Like synth3d from Maxar for geospatial and mapping. Synthetic voice and language models make radio communication more alive. But it can cost multiple million dollars a year to operate. Consider how small the DCS player base and spending power, most of those are not economically viable . They will wait until those technologies become much cheaper and easier to access.

2023-10-22 18:35:16.250 INFO DX11BACKEND (23688): NVIDIA API init OK 2023-10-22 18:35:16.252 INFO DX11BACKEND (23688): AtiAPI_Initialize Error 2023-10-22 18:35:16.252 INFO DX11BACKEND (23688): GPU count:1 And I noticed that the code normally shouldn't execute into ATI Initialize branch on a single NV GPU system. There is no "Display Driver Version" information in the logs. mov rcx, cs:qword_NVAPIstuff test rcx,rcx jnz doATIStuff It means there are nvapi64 or NGX API errors (nullptr) to get into the ATI Initialize routine. which is contradictory to "NVIDIA API init OK". and GPU count:1. The cause is unknown to me. Users who share similar logs with @Topper81 probably need use DDU to do a full graphic driver uninstall. then make a clean graphic driver reinstall. Make sure no weird registry values remain in system and no modified/outdated dlls. Your case is too unique. @Topper81Please direct contact with the developers. I cant do any further investigation. https://www.digitalcombatsimulator.com/en/support/

if you crash that often. for that long You should contact ED support directly. Dev will reply in a few working hours. https://www.digitalcombatsimulator.com/en/support/ Based on the context I found in the dmp file. Your most crashes are all related to the lua loading and memory alloc processes in Edcore.dll. make sure you have cleaned up and repaired all your game . Monitoring your memory usage during loading. anyway. Just create a ticket and contact the developer. We can't see through those memory dumps.

there is nothing new in this idea. There is just no commercial value in ED making this happen. DCS has very sophisticated export and import functions. from sensor data to imagery, etc.. and accept input through multiple channels. You learn a little bit of Python and use existing machine learning packages/models. then you can start train it today. Someone has already tried some interesting things: However, it was quite different to make it an actual working, economically viable, and profitable product. If there is commercial value, they could just outsource it to professional machine learning company, would be faster and cheaper; they wouldn't need to risk their money and manpower on something not in their expertise. The current existing ED game system is enough to feed the training cycle. And as long as we have enough players like you willing to pay. We may have a chance.

cloneInZone returns the func teleportToPoint() -> func dynAdd(ng) -> returns the "newgroup", a table copy of whatever passing though. which means this table follows this structure: groupData = { ["visible"] = , ["taskSelected"] = , ["route"] = { }, -- end of ["route"] ["groupId"] = , ["tasks"] = { }, -- end of ["tasks"] ["hidden"] = , ["units"] = { [1] = { }, -- end of [1] }, -- end of ["units"] ["y"] = , ["x"] = , ["name"] = "", ["start_time"] = , ["task"] = "", } So the name is "NewGroupName.name"

If you have RTX cards, Please try DLDSR or DSR super sampling; you are still able to render the image at much higher resolution for a better AA result. https://www.youtube.com/results?search_query=DLDSR+DSR https://search.bilibili.com/all?keyword=DLDSR If you have AMD cards, you should use RSR super resolution. https://www.youtube.com/results?search_query=AMD+RSR https://search.bilibili.com/all?keyword=Amd+RSR DCS only use your current screen res as baseline, so in order to make those feature working you need set to exclusive full screen or set your native desktop resolution to DSR/RSR resolution too. And you can combine DLDSR with DLSS, and RSR with FSR with bit of blur if your card unable to handle full 2x 4X resolution.

Your ST is running with SteamVR your MT is running with openXR Make sure you have setup your headset for openXR runtimes properly. Please use internet search guides about your headsets specific guides enabling it. you can add "--force_steam_VR" (without quote) as launch param in your shortcuts, force using steamVR runtimes.

Did you use any DLSS mods or DLSStweakers? They were not supposed to be there unless you have manually change the registry or use DLSS dll mods. This window is a DLSS debug indicator. Delete or set registry key "ShowDlssIndicator" to 0 in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore If you have nvngx.dll dxgi.dll mods please remove those mods as well

If your dcs crashes. Please post your own dcs.log and crash dmp files. Zip the entire folder upload to the forums. Unfortunately not every crash is traceable. But if dcs create one crash log. It makes things much straight forward.

Log shows DXGI_ERROR_DEVICE_REMOVED Which means Your graphic driver crashes. GPU is unresponsive. This really nasty driver or gpu crash. Not looking good.. Try a clean reinstall newest NV driver. Does your 2d monitor black or glitch too? Have you edit the tdrlevel tdrdelay value in the registry?

DLSS DLAA FSR only avabile at MT open beta. multithread preview version. DLSS require you have RTX cards. driver version>500. Windows version above win10 Fall 2017. For steam VR users: If you still have problems. post your DCS.log file

lot of people have good luck with this thread. too many P+E core cause some problems, and check Win11 powerservice "core parking" too.

If you have 11~13 gen cpu with more than 8 cores (p+e) please give this post a try. there is workaround about weird performance lost due to hyperthreading , too many cores But most people have good luck with turn off e core in bios or disable core 8 in taskmanager. addition If you are playing on win11 you try disabling powerserivce or "core parking" your log did not generate any crash dump. so the DCS is completely hanged before it crashed, cant really extract too many information from it.

@Flappie @BIGNEWY 2023-10-22 18:35:17.680 INFO DX11BACKEND (23688): NVIDIA DLSS not available on this hardward/platform., FeatureInitResult = 0x00000001, info: N After some ref from "NVIDIA DLSS Super Resolution Programming Guide" and DLSS SDK dx11backend.dll is somehow unable to capture the full "NVSDK_NGX_Result" string The NVSDK_NGX_Result strings in your files were encoded as "UTF-16". null but this line is UTF-8: "NVIDIA DLSS not available on this hardward/platform., FeatureInitResult = 0x%08x, info: %ls" And the "info:" part is where print the "NVSDK_NGX_Result" i can safely assume the ed_vlogf() function is also can only print UTF-8 . So it was unable to print the UTF-16 string fully and only print the very first character "N.". info: N This bug makes the user-end log incomplete. Make it impossible to troubleshoot with "NVSDK_NGX_Result". I'm not sure if your team is aware of this? Some refence:

Can you enable DLAA DLSS in non-VR mode? Have you installed any VR mods that enable FSR before ?(remove them)

In that cases, most of us unable to track the dmp file, so only ED can investigate this issue. We dont know how long they will notice your problems If you are in urgent, you can contact dev team directly and upload your dump and logs to, https://www.digitalcombatsimulator.com/en/support/ the dev will reply in few work hours or days