SkateZilla

The General Launch Button does not inherit VR Arguments. --force_enable_VR --force_OpenXR should work for launch arguments.

The Sparrowhawk and it's interface systems are part of that classified manual...

Aint gonna happen.

Why are we using time frames provided by another Dev Studio? DCS is not Star Fall.

The Code path's for the binaries are the same for steam and native. The only difference is the distribution protocol, and removal of DCS_Updater.exe and it's references. The Builds are identical outside of those changes.

Please Attach a Copy of the App Log File. Please attach a copy of the App's Log File and a Screenshot. I will also test on my end, as I think MS changed the .net command for ignoring DPI Changed both Windows Scaling and Text Scaling and saw no Change in the App's Text.

The Settings save when the app closes, Windows Force Closing is the same as End Process, so it doesnt save, I will add a save button somewhere indiscrete.

There are aspects of the Late F-14B's that are also classified and no public data on.

My screenshot above clearly shows the strips move with the canopy. along with the mirrors.

Correct, -Auto Update and Companion Updater App were removed until my webhost issues are resolved. -Window Size is hardcoded.

This would create the problem of Having to Support 4 Separate Code paths for RELEASE/OB Alone, not to even mention developmental builds etc. (ie ST-AMD, MT-AMD, ST-nVIDIA, MT-nVIDIA). DCS is Moving to Vulkan, not DirectX 12. That wont happen, Splitting the code paths between nVidia and AMD that is, as both are supposed to conform to the DirectX / Vulkan Standards in their drivers, if one has a problem over the other, 99% of the time it's driver related, as the DirectX API translates the instructions to send to the GPU Driver, which sends them to the GPU. (the Driver is the Bottleneck that Creates the CPU Overhead and Instructions bottleneck). With Vulkan it will be the same, Minus the Driver, Vulkan API translates the instructions and Sends directly to the GPU. Image Scaling is Image Scaling, they in principle function the same. nVidia's DLSS 1.0, Spatial Upscaling, uses the tensor Cores to accelerate the process nVidia's DLSS 2.0, Temporal Upscaling, uses the tensor Cores to accelerate and use AI to analyze the motion vectors. nVidia's DLSS 3.0, Temporal Upscaling, uses the tensor Cores to accelerate and the AI to analyze the motion vectors as well as generate intermediate frames. AMDFSR 1.0, Spatial Upscaling, uses the GPU Shaders to accelerate the process, Like DLSS 1.0, minus Dedicated Computational Cores. AMDFSR 2.0, Temporal Upscaling, uses the GPU Shaders to accelerate the process and analyze motion vectors, minus Dedicated Computational Cores. AMDFSR 3.0, Temporal Upscaling, uses the GPU AI (on rDNA3 or Zen4 APUs) or Shader Cores (on rDNA2) to accelerate the process and analyze motion vectors, as well as generate intermediate frames. Single Thread and Multi-Thread are only separate because Multi-Threaded DCS is still in Preview / Testing. It will not always be separated. MT Will eventually fully replace ST. DLSS is a generation ahead of FSR. DLSS performs better than FSR most of the time due to separate AI Cores doing the work, vs FSR utilizing Generic Shader cores. FSR 3.0 will Catch up with DLSS3.0 in performance and features, but DLSS3.0 has already been out for just under a year, FSR 3.0 is still being developed, and no release date has been set. FSR 3.0 will add Intermediate (Interpolated) Frame Generation, as well as Utilize the rDNA AI Cores on rDNA3 and Zen4 APUs. and rDNA 4 is expected to give significant hardware upgrades in both Ray Tracing Cores and AI Cores. FSR3.0 will supposedly function on rDNA2 and rDNA by continuing the use the Shader Cores (w/ Decreased Performance). That's all Assuming ED even decides to integrate FSR, as the AMD GPU Market Share is still under 30%.

There currently is no way to make the window larger/smaller, the 1400x850 is the hard coded resolution for the immediate future, Further down the line, I may re-configure it to allow the window to grow. However, Going into this version the % of users polled w/ a resolution less than 1080p was less than 3% out of 500 responses. There's simply no way to include all the data and features in a smaller window, originally the UI was 1920x1080p hard coded. I sacrificed a few things and re-configured a few features to get it down to 1400x850. There is no "Auto Update" as of right now, it will have a line across the top of the app when there's a new version available, and it will always be in the first post of this thread. As for Position Memory, on the App Settings Tab, when the option is enabled, it will save the window position when closing, and restore that position when opening.

the Cx5 Access Violation can be a number of things, not just System Ram, but anything that has a Memory Address, From Ram, to Vram, to USB Devices, to CPU Cache, they all have memory addresses, if the Memory Address ("at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx") in the access violation's trace back to the same device then the problem would be that devices. This is related to Device Switching and Power Profiles. "AmdPowerXpressRequestHighPerformance" is a driver call to request High Performance Profile, I would check your CPU for stability, as the crashes are related to FM Calculations and Performance Profile Driver Calls. Would also check GPU, as you only have 4GB of VRAM and that's cutting it very slim.

that sounds like a risky idea, as it may ping itself for version info much like my app does, I can maybe try to integrate an alternate check for the TrackIR slot, for OpenTrack files and if detected set them as the launch files and Rename the Button to OpenTrack and import the icon. the only issue would be if a user has both, it will always default to the trackir

it's keyed to the TrackIr5.exe, as that's what it looks for when it runs TrackIR check. In My App? Under Launch Buttons there's a Multi-Threaded ON / OFF Toggle. Also, ModelViewer does not work in bin-mt.

Argument 0027 is controlled by the country the aircraft is assigned to during mission load.

That Reminds me I need to add shortcuts back for /Appdata/Local/Skate Zilla Simulations/ to help with user.config issues.

Did you set it? Put it somewhere else and create a shortcut? I will see if I can code a way for it to inherit it's own filename and relay that to the function that scans for the app's filename. But I think I looked into this with the old app and never was able to come up with a solution.

Manual is being worked on, but some parts need to wait until sections of the app are done.

Problem is Virtual Pilots take that "Lore" as Law, When most of those stories are exaggerated stories exchanged between pilots that eventually were published in writing or video otherwise, without a shred of evidence to prove the scenario actually happened, despite the laws of physics, 20 Gs would kill anyone and the wing box of the tomcat would be destroyed, causing both wings to detach. I was in the hanger for most of the 90s, hung out with pilots, sat in tomcat pits as they told me stories, as a teen, it was cool to hear them, as an adult that knows more about aeronautics and physics, they are complete bull hardy. Then again, so where the stories anyone told us growing up..

<double post>

the 3D VCACHE is Sensitive to high frequencies...

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.