Marduk879

I can confirm the latest version 36 fixes the problem with the SG folder being named just "DCS". Thanks!

I understand that but renaming your SG folder means it fucks your game because it wont be able recognize its own SG folder and creates a new one? It basicaly means you get yeeted back to default in everything and you loose all your keybinds for example? Not to mention problems with 3rd party apps like SRS who would have incorrect SG folder path aswell because of the rename. Maybe i just dont understand this correctly. Anyway all this shouldnt matter at all if I directly define the folder the app should accept it and not do its own thing and ignore the defined path. This worked in 32 and no longer works in 35.

So i have the same problem as many others with the saved games folder. The app simply isnt able to recognize it and wont detect it. My problem is probably tied to the fact that my SG folder doesnt have build suffix as you state. My SG folder is simply named "DCS". This wasnt a problem in version 32 and is only a problem in version 35. I have done complete "reinstall" (deleted all app data in Local and unpacked fresh exe from the zipfile). Heres the console log from the app when i try to set up SG folder in version 35: 07.31.2023 | 11:34:21 dop. | APP | Log Screen Cleared 07.31.2023 | 11:34:30 dop. | SCAN | Launching Sim Scan Engine 07.31.2023 | 11:34:30 dop. | SCAN | Scanning ED Installs 07.31.2023 | 11:34:30 dop. | SCAN | Detecting Build Slot #1 Platform 07.31.2023 | 11:34:30 dop. | SCAN | DCS World Detected 07.31.2023 | 11:34:30 dop. | SCAN | Detecting Build Slot #1 Updater Platform 07.31.2023 | 11:34:30 dop. | SCAN | DCS Updater Detected 07.31.2023 | 11:34:30 dop. | SCAN | Detecting Build Slot #1 ModelViewer Platform 07.31.2023 | 11:34:30 dop. | SCAN | ED ModelViewer 2.0 Detected 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Build Slot #1 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 ED Sim Detected 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 Version Number: 2.8.7.42718 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 Open Beta Branch 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 ED Updater Detected 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 ED ModelViewer Detected 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 Variant Path File Not Found 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 Auto-Setting Default User Profile Path 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #2 - Sim Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #3 - Sim Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #4 - Sim Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #5 - Sim Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #6 - Sim Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | Scan Complete 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Saved Games 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #1 - Saved Games Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #2 - Saved Games Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #3 - Saved Games Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #4 - Saved Games Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #5 - Saved Games Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | SIM BUILD SLOT #6 - Saved Games Path Empty, Skipping 07.31.2023 | 11:34:30 dop. | SCAN | Updating Versions in UI Elements 07.31.2023 | 11:34:30 dop. | SCAN | Scan Complete 07.31.2023 | 11:34:30 dop. | INFO | Duration 0 hr : 0 min : 0 sec 07.31.2023 | 11:34:30 dop. | APP | Scanning For Build Selection 07.31.2023 | 11:34:30 dop. | APP | No Build Selected 07.31.2023 | 11:34:30 dop. | CHECK | Saved Games Not Detected 07.31.2023 | 11:34:30 dop. | WARNING | Set PRESET to DEFAULT 07.31.2023 | 11:34:30 dop. | WARNING | Disabling PRESETS 07.31.2023 | 11:34:30 dop. | WARNING | Disabling PRESET EDITOR 07.31.2023 | 11:34:30 dop. | WARNING | Disabling SERVER EDITOR 07.31.2023 | 11:34:30 dop. | SCAN | Initiating Module Scan: 07.31.2023 | 11:34:30 dop. | SCAN | Scanning for User Autoexec.cfg 07.31.2023 | 11:34:30 dop. | SCAN | DEEP SCAN MODE IS OFF, ADDITIONAL INFO WILL NOT BE SCANNED 07.31.2023 | 11:34:30 dop. | LOAD | User DCS Autoexec.cfg Loaded 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Jet Aircraft Modules: 07.31.2023 | 11:34:30 dop. | SCAN | Scanning for User DCS Updater Custom Scripts.bat 07.31.2023 | 11:34:30 dop. | LOAD | User DCS Updater Custom Scripts.bat Loaded 07.31.2023 | 11:34:30 dop. | APP UI | Generating Chart For Build Statistics 07.31.2023 | 11:34:30 dop. | APP UI | RESETTING BUILD STATISTICS CHART 07.31.2023 | 11:34:30 dop. | APP UI | BUILDING CHART FOR BUILD STATISTICS 07.31.2023 | 11:34:30 dop. | APP UI | BUILD STATISTICS CHART RENDER COMPLETE 07.31.2023 | 11:34:30 dop. | APP UI | Generating Chart For User Profile Statistics 07.31.2023 | 11:34:30 dop. | APP UI | RESETTING USER PROFILE STATISTICS CHART 07.31.2023 | 11:34:30 dop. | SCAN | DCS Jet Aircraft Modules Installed: 0 07.31.2023 | 11:34:30 dop. | APP UI | BUILDING CHART FOR USER PROFILE STATISTICS 07.31.2023 | 11:34:30 dop. | SCAN | DCS Jet Aircraft Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | APP UI | USER PROFILE STATISTICS CHART RENDER COMPLETE 07.31.2023 | 11:34:30 dop. | SCAN | FC/MAC Jet Aircraft Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | FC/MAC Jet Aircraft Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | APP UI | Generating Chart For PRESET RESOURCE 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Propeller Aircraft Modules: 07.31.2023 | 11:34:30 dop. | APP UI | RESETTING PRESET RESOURCE CHART 07.31.2023 | 11:34:30 dop. | SCAN | DCS Propeller Aircraft Modules Installed: 0 07.31.2023 | 11:34:30 dop. | APP UI | BUILDING CHART FOR PRESET RESOURCE 07.31.2023 | 11:34:30 dop. | APP UI | BUILD STATISTICS CHART RENDER COMPLETE 07.31.2023 | 11:34:30 dop. | SCAN | DCS Propeller Aircraft Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | No Preset Data for Home 07.31.2023 | 11:34:30 dop. | SCAN | FC/MAC Propeller Aircraft Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | FC/MAC Propeller Aircraft Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Rotary Wing Aircraft Modules: 07.31.2023 | 11:34:30 dop. | SCAN | DCS Rotary Wing Aircraft Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | DCS Rotary Wing Aircraft Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning For Campaign Modules: 07.31.2023 | 11:34:30 dop. | SCAN | Campaign Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | Campaign Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Theater/Terrain Modules: 07.31.2023 | 11:34:30 dop. | SCAN | DCS Theater/Terrain Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | DCS Theater/Terrain Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | FC/MAC Theater/Terrain Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | FC/MAC Theater/Terrain Modules Total Size: 0.00 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Asset Pack Modules: 07.31.2023 | 11:34:30 dop. | SCAN | DCS Asset Pack Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | DCS Asset Pack Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Tech./GPS Modules: 07.31.2023 | 11:34:30 dop. | SCAN | DCS Tech./GPS Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | DCS Tech./GPS Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Discontinued / Unsupported Modules: 07.31.2023 | 11:34:30 dop. | SCAN | Discontinued Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | Discontinued Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Unlicensed Modules: 07.31.2023 | 11:34:30 dop. | SCAN | Unlicensed Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | Unlicensed Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Scanning Utility Modules: 07.31.2023 | 11:34:30 dop. | SCAN | Utility Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | Utility Modules Total Size: 0 GB 07.31.2023 | 11:34:30 dop. | SCAN | Total Modules Installed: 0 07.31.2023 | 11:34:30 dop. | SCAN | Scan Complete 07.31.2023 | 11:34:30 dop. | INFO | Duration 0 hr : 0 min : 0 sec 07.31.2023 | 11:34:30 dop. | APP UI | Generating Chart 1 For Modules By Category 07.31.2023 | 11:34:30 dop. | APP UI | Complete 07.31.2023 | 11:34:30 dop. | APP UI | Generating Chart 2 For Modules By Size 07.31.2023 | 11:34:30 dop. | APP UI | Complete Heres App screen if you need it:

Where are the preset files supposed to be located?

Flew Su-25A on Enigma v2 cold war server. Started with around 80fps on ground an quickly degraded to like 25fps with large stutters over a time period of roughly 45mins. Unfortunately cannot attach the trk file as it exceeds the maximum size limit even compressed and zipped. null

Running the repair is useless. Makes you shut down the plane and wait 3 minutes while its a job the ground crew should during the rearming process. Im asking to provide clarifications: 1) How and when the gun jams happen? What are the cirmustances that must be met for it to happen? 2) Are all guns on ww2 fighters treated same or is it only 151 getting jams?

Hi, Today i took the Anton for a spin on a singleplayer training mission and during shooting on AI P51 in a turn the left MG 151/20 stopped shooting and according to debrief it was due to "gun overload jam". Heres the debrief: Random failures are off. What exactly are the conditions for this to happen? They seem really strange and ive never read anywhere about MG151s being prone to jams. Also to my knowledge allied planes do not suffer jams or stoppages (I own the P-51). Whats the difference between these weapons that the 151 jams and the Hispano on Spitfire for example does not? (Which by the way is ironic because early and mid generation Hispanos were notorius for jamming because all sort of reasons) Second part of my bug report and question is that ground crew does not unjam the jammed gun when they reload it. How exactly ground crew does this? Are they magicians? Attaching TRK and DEBRIEF file: FW-190A8_training.log FW-190A8_training.trk

They cant because they would get arrested or get in trouble or whatever! See? Its bulletproof strategy.

I can confirm i have the same problem as Parab. Easily replicable on any MP server. I Just go Enigma CW get into frontline just when the radar is ready and after turning it on it takes like 10secs at max to kill all my frames. Usualy a drop from 60 fps to like 15-25. My rig: CPU: i7-3770k GPU: Asus ROG STRIX GTX 1080 8GB RAM: x HyperX Fury Black 32GB (4x8) PSU: Corsair HX750 HDD: 2xWD Caviar Black FZEX 1TB SSD: Crucial BX100 250GB NAND: Intel SSD 660p, M.2 - 512GB MB: ASUS P8Z77-V PRO DCS is on the M.2 drive. If you need any sort of logs or tracks provided let me know.

Add Mosquito to blue so i can bonk it with the 37mm

Maybe Fw-190 A-8 for red as CAS plane?

Yeah still really bad here.

I was testing this today and i found out that this radar perfomance drop is only happening for me when the MSAA is set to 2x, while MSAA 4x this bug never happened. Very strange!

Im glad he showed mercy to us unimportant plebs on the server trying to spend our free time for fun which we could aswell spend somewhere else. Please relay to him he will be in my prayers. "I wont destroy ALL of your EWRs just some you know..." Jesus fucking christ what an attitude... Im sorry but i had to react. Im here hoping its just bad wording and he really understands the problem.

Hi, Draconus and Klarsnow claim that full rudder deflection above mach 1,5 isnt possible due to system limiting rudder deflection but Rex is able to get full deflection at mach 2. I dont understand how is this possible. Probably the mentioned system isnt implemented or isnt working then?

I discovered the unit stationed in Netherlands(No.41 Squadron operating from Twente) aswell and the only info about their task was V-1 interception. Over NL and the channel i guess? No mentions about tasks as cover in CAS missions or other like covering bombers, ground troops or fighter sweeps. The only mentioned thing including enemy fighters is when on "anti-jet patrol" a group stumbled upon 109 and 190s.

Maybe youll correct me here guys but as far as my info goes no griffon spits were deployed as frontline(meaning on continental Europe). Most of them were reserved as V-1 interceptors on British isles. Possibility of K-4 meeting MkXIV is goddamn low.

Dont forget AI do not follow the same law of physics as players do. They have simplified flight model allowing them to do manuevers players can never follow or do the same.

+1 same here

@Magic Zach i dont understand how you came to a conclusion a section named "weapons for air-to-air combat" has something to do with something called "Anti-aircraft command" which both in US and GB came into existence AFTER the war (1950 for US). Please elaborate This document is about US Ordnance Department during World War 2 and includes everything from infantry rifles to bombs. This department was responsible for supplying the whole US army and all its parts, be it ground force or air force, with weapons,munition and all other ordnance needed. You are right in that the document does not specify the belt compositions. The ordnance department recommendation can be simplified down to "Dont use the M8 round. Use the AP and Incendiary rounds as you did before in whatever belt configuration for general air to air combat and use AP for ground strafing until we find solution." Thanks for your reaction. If you decide to keep the M8 round in the belts take into account the ordnance department report on it about its decreased penetration and incendiarsy effects. This should be somehow reflected in DCS.

@NineLine Hi i would like to bring your attention to this document - "THE ORDNANCE DEPARTMENT: PLANNING MUNITIONS FOR WAR" by Conslance McLaughlin, Green Harry C. Thomson and Peler C. Roots At page 430 paragraph "The Problem of Effective Striking Power" is interesting to our problem of USAF ammo belts during WW2. Mainly this part is very interesting: According to information from this the correct belt compoisiton should be as follows: General air combat belt: AP/AP/I/I/T Alternatively there can be belt with tracers only at the end which signaled the pilot that he is out of ammo. This was known modification. If you decide to include the M8 round in the belts anyway it should neither achieve the penetration power of the M2 AP round nor the incendiary power of M1 round. Ground strafing: AP/AP/AP/AP/T Next part of the same paragraph describes the development of the API rounds which became available close to the end of war in 1945: M20 M23 This can further open possibility for belts filled with the newly available API ammunition - M20 and M23 if the scenario is late 1945 or the scenario maker allows it. Link to the complete document below as its total size exceeds the maximum size of attachment here on forums: https://history.army.mil/html/books/010/10-9/CMH_Pub_10-9.pdf The whole "CHAPTER XV Aircraft Armament: Weapons for Air-to-Air Combat" is worth a study and may contain more information relevant to this topic.

How could you accurately set this value when you dont know how the code works? Or do you mean that just you specificaly dont know how it works? Maybe its about time someone who actualy KNOWS how it works tells us plebs? Im in really big doubt here because when you look into the lua files theres alot of commented text for variables in this section stating that even ED devs(or whoever puts them there) dont know what they mean or do.

The thing we dont see is how many times Mad got shot down in the Anton before he got enough material for this vid :)

Im not sure what you mean here? Are you trying to play it here into the area of "Not EVERY SINGLE ONE A-8 had EN and thus we wont implement it."? Ofcourse it wasnt 100% of all A-8. Units upgraded their planes as they received the EN upgrade kits and other parts. Shortages were ever present for LW. July 1944 marks a point when all new A-8s that left the factory had EN already installed.

This was dealt with by moving the bombrack ETC 501 forward 20cm. So if you got the extra fuel tank behind the pilot you should keep the bombrack to eliminate the gravity shift.