SkateZilla

Attached to First Post. 7.10.2023.33 - Corrected Mis-Link of LocalSource Params in "Update All" Function. - Corrected Null Value in User Profile "Config" Copy/Backup/Delete Function. - Added "Build Name" to Config Backup folder name. - Revised About Page Info and 3rd Parties List. - Revised Splash and App Logo. - Adjusted Splash Text alignment. - Integrated User Option to Remember Last Known App Screen Position. - Adjusted Font Sizes on Most of the Tabs (Further Tweaking to come). - Added SZS Facebook Button and ED Forum App Discussion Button to About Page. - Depreciated Updater Settings Button/Label will hide unless within Version Threshold. - Rewrote Preset Import Functions (Presets will now save after importing from another Preset). - Adjusted Layout of all preset editor controls. - VR Preset Tab Page Completed w/ all Missing Options for VR. - Minor Tweaking to Thread Order. - Created Custom Textbox Control to eliminate theme problems. - Tweaks to Theme Colors when using Alternate Tab Style. - Team Red Theme Added. - Enabled Per Build Multi-Thread Mode Setting.

They maybe concealled by illusion, as they'd be about the same position as the farther canopy rail, therefore "Hidden" at that angle. I can definately barely make out the RIO Rail. I can assure you they are there though.

There is no auto-update at the moment, The App itself checks the server for latest build version and build date and it populates the top bar of the app. Ie: Once I get a new host worked out, I'll re-enable and add the updater back to the package w/ the ability to update itself.

Passing Memtest86 when nothing else is running doesnt show if there is a power problem. You need to run a Memory Test in windows, while running a CPU Test to draw power from the board. You really shouldnt have any issues with IMC Voltage problems running only 2 sticks. Make sure you have the correct XMP Profile set for the sticks as well.

The Updater code is done, but not integrated due to hosting issues / terms, I've lost 3 different webhost provider accounts under terms that they do not allow App Deployments from their webservers (apparently it's a big thing in some countries (sus companies hosting fake apps w/ virus')), so a lot of hosting companies shut down accounts that do this. I even had a webpage on my last webhost so they would see it wasn't simply app deployment. There is automatic notification of a new version on the top of the app, I may make it clickable and have it bring users to this thread, where the app would be hosted for the time being.

Per Manual for your Mainboard:

You mean have the ability to choose and launch different scripts? can you elaborate more? Also, please elaborate on dcs.exe unloaded, like what type of function ( I would need an example to determine viability) There's Folder Icons for each build, and they have tool tips that explain what they are.

Moving folders creates a new APPDATA url Code. you can goto the APPDATA/Local/Skate Zilla Simulations/ Folder and copy the settings file from one folder to another.

No, Previous Version used an entorely different code path. Im tracking this as well, it appears it was unable to update and save any values according to the log file. I Hope to have a resolution soon. Edit: 7/0//23 @ 1830 EST: Log Files Provided plus a slow scan over the Import Slots 1-4, Custom 1-3 + Browse for File Import, I was able to pinpoint the problem and re-write the import function to resolve the issue. You mustve missed my 2 previous replies to you regarding these functions being broken by a null value. But the Individual Folders when deleted should goto recycle bin, backup to the set backup folder. The Source / destination is meant for copying the entire /Config Folder from one build to another, backup makes a backup and delete sends to recycle bin. However a null exception in the last few builds basically messed this entire page up.

Which Setting button? They can be deleted in User Profile Management: or After Update:

Removing it would end requests to expand it, and also remove any issues with it being interlaced with the EFM down the road.

V1 Also had the Problem of Loading off screen due to end user monitor config changing and coordinates no longer valid. Remembering the Position is easy enough to re-enable and put an options toggle, I will add to the flow board. A Mod Manager was part of the Alpha, but it was not in a state that was usable and holding up the release so it was removed.

but yeah, those numbers are uninstalled power plants They were tuned to 17000~ (70lbs +/- depending on revision and fuel), on F-14As

never said it was 2000 lbs per power plant.

F-14A (TF30-414A's) max thrust is 20,900 Each, as was TF-30-414 and TF-30-412s F-14B/D (GE F110-GE400) max thrust was 26,950. The main A/B-D Difference was no compressor stalls, better throttle response, ~60% Power Increase in Max Military Thrust, and ~30% Power Increase in Max AB. Thus the B/D Tomcat had more power in Max Military it did in the lower AB Range. Better T:W Ratio, Less use of AB in BFM and Takeoff, More Fuel, More Loiter Time.

yeah, I guess NOS button was a bad example, more like a Safety Throttle Limiter (ie STM and TCS). The System will only affect the thrust in the situations it's designed to prevent compressor stalls. so it's not really a "Boost" but more so Disabling a "Limiter" (well the system doesn't limit parsey either, it more or less engages a safety mechanism that causes a thrust penalty of up to 5%, and honestly I think the 5% is in reheat and only 2% max penalty in Military thrust. But Basically Like Turning off STM and TCS on a hot Dry Straight Race Track, vs Turning it Off on a Turning Wet Track, lol. Turning it off straight and level does nothing, turning it off in a high AoA with stop the system from engaging and thus not incur the thrust penalty under high AoA but substantially increases the risk of a compressor stall. I don't think the breaker existed to facilitate a BFM Edge, it existed as a way to disable the system / circuit had it sustained damage and needed to be shut off to safely return to base/boat. If it was designed to be disabled to give a Dogfighting edge it would have had a switch in the pilot cockpit somewhere, and not a remote breaker off to the right that neither Goose or Rooster couldn't find in a hurry if they wanted too.

As I said in the other thread..... I'd honestly rem the code/system entirely, Users got the idea that popping the breaker was equivalent to pressing the NOS or TCS Off button on a race car. (More power at the expense of stability etc). the issue here is, the over the top story in a book or video interview was over hyped to get the viewer/reader excited, I know pilots that literally laugh at this, and say they would never use such an high risk tactic, ever. Why would you risk compressor stall and losing your aircraft for a measly 2000lbs of thrust (out of a total of 41,800)(aka ~5%), when you can better manage AoA, G's, turn rate and maintain speed without any risk. If you desperately 5% more total thrust to win all your engagements, your doing something wrong.

That's not to say, Some Font's and Controls / text may get a small enlargement, as I made them small in the UI originally to fit everything, I've since divided or moved many controls around, so there is space, to not have Microscopic 8 pt fonts on many of the controls.

1. Scalable Window isn't an option at the moment, as many elements are hard coded to their size/dock/location, I could add a pop out console w/ a larger font size, but I wouldn't say that it would be a priority, as I have other major functions that need to be finished and debugged. the UI Window is already substantially bigger than what most users wanted (apparently people still use 1280x720p displays?). when I have time to re-configure the docking and linked edges of the controls, I may have the right side extendable and as the app window size extends past specific values, increase the font size of the console. 2. and 3. are being worked on, Like I said, I have to be careful how it's integrated to remember, and when the value is loaded as there are dozens of sub functions tied to preset switches, and if the app switches from default to another before all the functions are complete it will cause a mess in exceptions and desync. Same for when a User chooses a Preset and switches builds. It would likely be a complex system that manages the selected preset the same way it manages the preset names per builds. Same for MT Switch, If it's enabled on a build that has MT then switches to a non MT build and it remains enabled, then it would cause argument manifest and binary exceptions. It'd also be a complex system that remembers MT Button state for each build but still run the MT check and disable if the MT Binaries are not preset. They'll both be integrated, but it's not going to be a rush job, and I have a significant list of little bugs in the core functions that need to have

That would be an Assumption.

All updates are attached to the first post: https://forum.dcs.world/topic/134493-the-dcs-updater-launcher-gui-utility-version-20-2023/

I'd honestly rem the code entirely, Users got the idea that popping the breaker was equivalent to pressing the NOS or TCS Off button on a race car. (More power at the expense of stability etc). the issue here is, the over the top story in a book or video interview was over hyped to get the viewer/reader excited, I know pilots that literally laugh at this, Why would you risk compressor stall and losing your aircraft for a measly 2000lbs of thrust (out of a total of 41,800)(aka ~5%), when you can better manage AoA and maintain speed without any risk. If you desperately 5% more total thrust to win all your engagements, your doing something wrong.

3rd Parties use EFM: External Flight Model, and the Fidelity can range anywhere the developer wants it to w/ the data they have.

For the record, my question regarding separation was Rhetorical. As for Rendering, 1 Model can easily take years w/ complex animations, damage models, texture research, PBR Layer Generation, etc etc etc. Outside of that, for DCS at least, it's not even about the new EDMs, you can clearly see they are in the sim in the 2023 Beyond and any ED Content published thus after, The models even if done, it's still not ready to fly, the AI Flight Models, AI Systems etc. likely aren't done. In Closing, The B-1B, B-52H, S-3 are more than "Model Swaps", And I'd rather wait for them to be properly done, vs ED Dropping the new Models in now, and continue to use any old and broken AI Scripts for said aircraft.

What would be the point of separating them if they are going to connect to the same servers, if that were the case it would simply be a new module.