Kanelbolle

Was this supposed to be posted here ? Forum and Site Issues - ED Forums

Good to hear it has improved.

You might want to have some documentation on this when posting claims.. just saying it might have happened is not reason for any investigation. Post your DCS log file if it shows this happening. PS: go through your log file and remove any sensetive informasjon if there are any before posting it. Screenshots of a monitor program that shows it also helps.

Unless you're 3090 is defective it is highly doubtful your 3090 can't handle DCS in any multiplayer server. I have a 3090 and have no issues on any DCS mp server. What SSD do you have? Reason I am askeding is because you have Windows 11 64 24H2 that has a known issue with WD SSD's. In general if you are a gamer, I would stay away from test builds of Windows and rolle it back to the previous version.

This is not something new to users making capture missions, been this way as long as i can remember. When dealing with the lack of capture event to the NEUTRAL coalition, i just have a variable/flag stored to check what the last known coalition of each airbase is, then run a scheduled function periodically to check if it has changed from blue or red to NEUTRAL. Would be nice if there was a event, but this has been known for forever and i have lost hope that it would be added/fixed. When it comes to revert ownership of the airbase i oppose your solution. At least how you purpose it. Mission makers depend on this to get it back to the original state, including me. If there where to be a solution to this, it would be to make it toggle on or off with the current native capture system active. Preferably per airbase and configurable in ME and by script. I think the behaviour of this is made to show that a country owns a airbase even if there are no units on it. This might not be behaviour you want in a fictional scenario, but it would be nice to have it toggle off or on.

Ah.. never heard of anyone doing that. Don't know why you would have to, I just use the joint coalition country to use anny unit for that coalition.

Not sure why you are trying to start DCS standalone through Steam? To get a example Xbox controller to work in DCS, you just add the controller to steam. Keep Steam running and then start DCS the regular way. Guide for Xbox controller: https://steamcommunity.com/sharedfiles/filedetails/?id=940724386

What fo you mean by adding units to different countries? As far as I know you can't add a unit to the country in ME at least. You can add countries to a different coalition. Example, you can move Russia over to the Blue coalition.

See you have a Intel 13Gen, have you updated your BIOS for your motherboard to the latest version with the last microcode? And of course use the Intel default settings. Do you experience any crashes in other programs? You can try running Cinebench and Memtest86+ to test your system stability.

Not everyone wants to wait for a patch to keep playing. Not rocket science.... Your basically saying nobody should try and play the game because the player has to lift a finger to get the game working again. Some are thankful that people try to help others, guess you're not.

no it doesn't know that... it might be unstable memory overclocking. So it suggests turning off any overclocking in BIOS and see if it is more stable. You can also try testing the memory with example: https://memtest.org/

you need static slots (not dynamic slots) and you need to put the slot blocking script in your %USERPROFILE%\Saved Games\DCS.openbeta\Scripts\Hooks\ or USERPROFILE%\Saved Games\DCS\Scripts\Hooks\ and it only works on a multiplayer server. not Singel player

You can go to Discord and post it in the ED log analyzer: https://discord.com/channels/542985647502393346/1179171301651402802 It will give you tips on what you can try. As far as i can see you have a mod called "ECHO19_FA18". If you have crashes, the first thing to to is remove all mods and run a full repair of DCS. Other things the analyzer points out: Errors Memory Timing Issues Remove any overclocking (XMP) from your RAM. The Integrity Check failed Delete all unofficial mods and do a !repair of DCS. There is a GPU-related error Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one. Tuning Tips Turn off SSLR. Enable Full Screen mode. Consider using DLAA. Turn off SSAO. Tuning tips are recommendations for better FPS based on your CPU, GPU and RAM. They might result in slightly decreased display quality.

According to your log file, your graphic settings are quite high. Just to test, try setting the "Low" preset in the Launcher or in-game and try the same. Suspecting it is your VRAM usage that is high, so it reaches max and tanks the performance. But might as well also be a bug. As far as performance in the F10 map alone, it is and has always been bad in "Altitude" mode. If you change it to Satellite or MAP mode, the FPS goes up.

Well as my check list allerede shows, you should focus on 2D first. VR isn't important until you have confirmed it is not an issue in general. If it has been confirmed it is a problem only in VR, then you can start troubleshoot VR.

Ben posted before but no track file presented: https://forum.dcs.world/topic/358812-combined-arms/#comment-5532929

Yea, not much to check then why this happened. If it happens again, take a copy of the log file and post it.

@Falcko You could also try and roll back the DCS version to make shure it is the DCS version change that caused it: https://forum.dcs.world/topic/94816-guide-info-dcs-updater-usage-version-numbers-module-ids/ But @NIAGARA MOHAWK Might also be on to something, if you updated Windows in this time period as well. But i would try rolling back DCS first. Uninstalling Windows security update can put your system at more risk.

@Nealius autoupdate_log.txt or/and autoupdate_log_old.txt in your main DCS game folder. Mine are in "E:\DCS World OpenBeta\"

Do you have the log file from where this happend? If it uninstalled it should show up in one of the log files.

I second the part that the log file is of no use here since you didn't actually play the game. The title is also wrong. Version number is incorrect according to the text. To state the obvious here.. the patch changes you have different performance between has changes to how terrain is handled in DCS. Might be a problem for ED to look in to, but I would start with lowering Graphics settings to the Low "preset" just to see if the stuttering is still there. If it is not, you know you have to lower your graphics settings untill ED fixes/improve the performance. You can also go through my checklist I use myself: 1. Disable the DCS Launcher and run the game directly from "DCS.exe" (not dcs_update.exe) in the "mt-bin\" folder. Some expariance stuttering in game when starting the game with the Launcher. (unknown why) 2. Try to update to the latest GPU drivers or reinstalling it. NVIDIA: Always use the option "Custom installation" and select "Clean installation". Not doing a clean installation sometimes causes issues. 3. Nvidia graphics card: Check 3d settings in Nvidia Control settings if you have a custom profile for DCS. Changing these might help. Have not checked if you need to add both DCS.exe files from "\bin" and "mt-bin" to this list and change the one you are running. 4. Disable VR and get the game running properly in 2D first at a good FPS. 5. Try setting the "Low" graphics preset for testing. 6. You can try this if you have a Nvidia GPU: Change "Background Application Max Frame Rate" to "ON" and example "100" (or what you want to keep it at) in "Nvidia Control Panel" under "Manage 3D settings". Start DCS and check if the problem is still there. It's a bug in the driver, if it's off... sometimes it does 30-40 fps. 7. Delete the content in the "fxo" and "metashaders2" folders from the saved games folder. ( usually under %USERPROFILE%\Saved Games\DCS.openbeta or USERPROFILE%\Saved Games\DCS ) 8. Run a cleanup and repair (slow repair) on DCS : https://www.digitalcombatsimulator.com/en/support/faq/709/ 9. Remove all MODS. (scripts and mod files that were installed) Might need to rename your DCS profile folder to be Shure. 10. Turn off hotplug under "Adjust controls". (Disables DCS from checking if a device was connected while the game is running.) In some cases this can cause lag. 11. Always have the game and your windows page file on a SSD drive (not on a regular HDD). Also check if you're low on space. 12. Check that your system components are not throttled by heat. CPU, GPU and motherboard. Example with HWINFO64 while running the game. 13. Streamdeck export scrips might cause issues, remove them from the game if installed to check if they are the cause. 14. Unplug any USB hub if you use one. Sometimes hubs can cause problems in DCS. (For testing, plugg ut back in if you have testet it and can confirm it is not causing issues.) When plugged back in go to Windows "Device Mangerer" -> "Universal Serial buss Controllers", open all USB devices and go to the "Power Manegment" tab and uncheck "Allow the computer to turn off this device to save power". 15. If you have Windows 10/11: Added both .exe files to the "Custom graphics settings" list in Windows Display settings. You can find it under "Display Settings" ->"Graphics" or "System" -> "Display" -> "Graphics" in Windows. Add both .exe files in "\bin" and "\mt-bin". Set it to "High Performance" 16. Check your Windows power plan/mode, change it to "Best performance". To change the power mode, select Start > Settings > System > Power & battery. 17. Your CPU might have parked cores, check your LOG file for this message: "CPU HAS PARKED LOGICAL CORES". Having Windows power plan/mode on "Best performance" should have fixed this, but if it does not you can search for the application "Parkcontrol". 18. Disable "Game mode" and "Game bar" in Windows. 19. Disable Tacview if enabled or installed. If it has no effect, you can enable it again. But it is recommended to Options -> Specials -> Tacview and set "Multiplayer flights - As Client" to "Record local player only", recording all might cause stutters.

At the moment you actually can move ammo without scripts with dynamic cargo and the Ch-47, but you can't count how much you moved. Anyway, if you are determined on trying to script it, I would look at this example: https://forum.dcs.world/topic/332300-warehouse-control-functions/?do=findComment&comment=5282893 local friendlyAirbases = coalition.getAirbases(coalition.side.BLUE) for i = 1, #friendlyAirbases do local w = friendlyAirbases[i]:getWarehouse() local inventory = w:getInventory().weapon for wpn, _ in pairs(inventory) do w:setItem(wpn, 30) end end And look at the get command: https://wiki.hoggitworld.com/view/DCS_func_getItemCount You can also take a look at this script that saves Warehouse inventory for clues: https://forum.dcs.world/topic/332310-script-release-simple-warehouse-saving-sws/#comment-5276682 But as i pointed out earlier, it's going to be hard building anything without the Lua experience. You should go through some Lua tutorials and learn the basic first

@Magic_Jim To be honest, if you are a beginner to scripting lua i would not recommend starting with warehouse control. It's not the easiest part to learn from. The things you want to accomplish is better to just simulate with triggers in the ME until you are further in to your lua learning phase. Here is an example you can use a trigger to check if the cargo is in the zone and lower then an altitude.

I have not been able to replicate this bug on any other map then Kola. Though I have not spent hours on other maps since Kola released.

Have not tried this code, but would think it works. Might be as simple as the name being case sensitive. I my self use the airbase ID when working with airbases. You can get out a list of the names by using this code: https://wiki.hoggitworld.com/view/DCS_func_getAirbases You just need to add : env.info(info.callsign) This will list all airbase call sign to the DCS.log or trigger.action.outText(info.callsign , 10) To get it in the message box up in the right corner in-game.