SkateZilla

Yes, your log file is the same as the other's im tracking, the startup hangs at the Build Scanner start after it checks processes. Also if you could provide log from when you attempt backup of files and it goes to the default folder vs the set folder..

There are a few new themes being worked on, but it's not a primary task. Also I am tracking a bug introduced in the last build before public release where over 70% of the module "Uninstall Functions" got mis-linked back to "Install Functions" I am looking into elevated process launches from Non Admin App running. if the App is run as Admin, any processes it launches should inherit the same elevation.

1. Good to hear as that's the way it's intended. 2. I am tracking this issue, once I find the root cause for the scanner to hang. I can fix it. 3. MT is the Default, ST is Legacy/Support Mode, which is why it's always on if it detects the MT Binaries, I may make it so it remembers the user settings.

This is the same problem another user is having, on Startup it hangs just before scanning builds, which is why it says not detected for everything. I am looking into the startup order for anything that can cause the Build Scanner to hang. I will have to Check, but IIRC OneDrive Folders are usually not visible to all apps. Check the log, it should state if the folder was not accessable. Not Currently, I am looking into some things, but font size is static and locked, All of the Black Background Themes are harder to read due to contrast of the Color on Black (Matrix and Tron Themes_.

Select Preset, Goto Preset Editor Tab, Now, IF you Choose one of the Global Presets or Import Options, You have to Click Save before moving any controls in the sections below (*will be fixed soon). if not you should be able to click and edit controls and click save. Now if the options.lua does not have a value for that control already in the file, it will not save it.

On the Home Screen on the Preset Selected Boxes there's a Tag and a Tag w/ a Slash Through it, Click the Tag. I plan to have a PDF for Instructions done soon, Also, Monday's are the Days when I commit new builds, barring a major issue or simply nothing has been changed.

if Open XR is Selected, it runs the command with the switch, ""--force_enable_VR --force_OpenXR"" But AFAIK, OpenXR only works in MT Mode. (will have to confirm, but that's what I was told by several others). I will also double check the switches.

Do you have more than 1 build or just open beta?

Try clicking on build scanner : active button, it should terminate the process, then click on a build button (the button w/ all the info and hornet on the background). Something on your system is causing the build scanner to hang.

Next time it fails to load, click on build 1's button and see if it triggers it to scan the build. I'll have to check into this deeper when I'm at my desktop, as I'd have to look at the codepath to see what is after the ED_ Server Scan and before the build scan. I'd recommend wiping the app settings and starting over %APPDATA%/Local/Skate Zilla Simulations/

I need logs for both so I can compare them. Because the log posted above, shows that no build is selected, so it never scanned for information from the binaries. For Example, the last one you posted After Line: 07/01/2023 | 09:55:22 PM | CHECK | ED Server Not Running It's supposed to start scanning installs for Binary Version numbers, but it jumps directly to opening the log. So something is stopping it from scanning the builds, Most likely because the path is inaccessible. in what order does the Successful / Unsuccessful launches occur?

Also what's the app look like when loading, ( Screenshot )

These Logs are for Versions of the App that are no Longer supported.

I would need to see the entire log for just the session. I may be the build scan is not able to access folders so it removes the folder and de-selects the build. When the App Launches initially, there is no build selected, once user paths are loaded and checked, it will then load the user selected build.

an Exception error may be occurring, like I said, the build scanner and module scanner are constantly updated, I'll keep an eye out for an errant exception that causes the function to stop instead of completing.

Delete the entire Config/Presets/ Folder, Delete or remove any options.presetxx.lua files as well. Launch the App, it will Populate new Preset Files automatically. Select a Preset, let it load values, note the log on the bottom of the screen, it will tell you which values are not able to be loaded because they arent in the file. Note: that the Editor will not save changes to any preset parameter that doesn't already exist in the file. in the future there will be some changes, as I plan to expand the options.lua parser and saving. Also note, the App Presets have Zero to do with the Presets inside the DCS Options Screen. They are 2 separate systems, one's ED's and requires you to launch into DCS to switch presets. The App's presets are self contained files that swap out at launch, so once in DCS, change whatever settings you want, and press OK (not Save to Custom1/2/3), or Configure them in the App and press save. Ok, Good to hear, I am constantly adjusting module scanner, so it wouldn't be all that surprising if it was false detecting something.

I will look into the scripts box, you can also force save a single line, then open /Saved Games/DCS Updater Utility/DCS Updater Custom Scripts.bat and paste the contents and save, then relaunch the app. this maybe due to user permissions. This maybe due to Windows putting the App in Sleep/Background Process Status instead of closing it, Open Task Manager, Processes Tab, and scroll down thru the background Processes and ensure windows did not put it in sleep mode, which will prevent new instances from launching. If it's not displaying version numbers then it's because when scanning for build the path or file was not accessible. My App does not touch the System Registry at all. OpenXR still requires Oculus App to launch, it will launch Oculus with OpenXR Libraries (evident by the OpenXR Overlay and options.) OpenXR also AFAIK only works in MT More. I will look into this, Pretty sure I had changed the value to allow significantly more, but it may have reverted. The issue with any color on black, would be Contrast Ratio, as evident by "Tron/Matrix" Color Scheme, the contrast to anything on black makes the text look horrible. I will double check the Loading routine, as it should set it to default, but if it's launching and remaining blank then I need to fix that. Multi-Threaded Button Defaults to on if MT Binaries are detected as MT is the default, and ST is now technically a "Legacy/Support" Mode. Make sure something isn't locking the files, or there isnt an options.lua in the /Default/ Folder (that's where the default is moved to when another preset is being used) As it's saying the files cannot be moved because it already exists, I will double check the scan, I have a few reports of modules being reported as installed. double check that /DCS/Mods/aircraft/Mi-24P/ Folder and entry.lua doesn't exist.

See First Post for DL: v1.1.0.1040 - > v2.0.0.31 Launch Change Log - New Completely Rewritten Core. - Supports Windows 10/11. - New UI (Uses MetroSetUI Library Controls). - Unified Exe (All Libraries are Embedded in the EXE, 1 File Distribution). - Multithreaded (Each Major Function has a Separate Thread from the UI, 12 Threads Total). - Moved to 64-Bit Exclusive Compiling. - Supports DCS 1.5+ (1.5->2.4 is now considered Legacy and have limited functionality). (1.2.6 and Lower are no longer supported but may still work.) - Supports 6 Active Builds Per Instance. - Allows 6 Graphics Presets Per Build (4 Unique Named Presets + VR and Default Per Build). - Supports all the DCS World Functions and Modules. - Expanded Build and Module Management (Size Charts/Data, Options to Backup/Delete Specific Folders). - Expanded Modules Management (Can install/uninstall unlisted modules, Several Filter Options). - Expanded Advanced Update Options ( New Install Initialization Function, Schedule to Update All Builds, Local Sources, etc). - Expanded Launcher Options (VR Runtime Selection, Arguments, Scripts, Autoexec.cfg etc). - Rewritten and Expanded Processes Management. - New GFX Preset Editor (Allows User to Edit/Import/Save Graphics Settings By Profile). - New Server / Host Options (Allows User to Edit/Save Server Settings Directly). - Revised App Settings. - App Themes.

False The FC3 PFMs are definitely not 20 years old. the Flight Models 20 years ago were Pre AFM, on Rails. Every FC3 Aircraft has had an External Model Revamp, Professional Flight Model Made, and 3D Cockpit Models Made in the last 8 years. So the 20 Year old statement is false. Also, I seriously doubt Any DCS Aircraft you'd be able to study in 2 Afternoons.

Block II Pre AESA and Some of the other defensive system upgrades, Pre HOL and Pre- ACS, is essentially Block I, w/ a few changes to the A18 heat sinks and vent system. You aren't gonna get anything in the block II+ generation as they transitioned to HOL OFP from SCS OFP, and I doubt Boeing would let the encryption for the HOL OFP to go public.

Trust me, if anyone wanted to see the super hornet it'd be Wags.. he was Part of the Jane's F/A-18 team waaaaaaaay back in the day.

F-15C was a Low Fidelity Aircraft, F-15E was a 3rd Party High Fidelity Aircraft, Not the same situation as A-10C Suite 3/5 to A-10C Suite 5/7ish, which were developed by ED for Professional Contracts w/ Permission to sell Entertainment Versions.

I cannot comment on expectations sorry.

The API Bottleneck can't be fixed, Which is why ED is Moving DCS from DX11 to Vulkan, Somewhere in the Vulkan Thread, I broke it all down in the Vulkan thread a few times.. but:

no GPU Currently on the Market even uses 100% of the PCie 4.0 x16 Slot Bandwidth. Why Add development expense to the card, just to add the PCIe5 Interface controller to it, when it offers nothing. The ONLY PCIe5 Devices I've seen are M.2s, and even the performance between them only benefits Sequential Writing, the Random Read/Write is pretty much the same between the two. Honestly, MT Added the Ability to Separate Rendering Thread from the sim thread, So Heavy Sim Thread Load doesnt Kill Rendering thread performance, leading to Low FPS / GPU Usage. The bottleneck now isnt the "GPU", it's the Rendering API (DirectX 11).