SkateZilla

Also, to reduce TAA / DLAA Smearing and bleeds, keep the frame times as low as possible, and the FPS as close to the headset's native as possible. in my experience, the smear/bleeding is barely visible at 75Hz w/ low frame times, once the FPS starts to drop, the smearing gets worse as the frame times go up, Longer frame times = more movement between frames = smearing / bleeding. Turning off Screenspace shaders and lowering rendering and water detail typically has good results.

MSAA + Post Process Effects = Stupid high frame times, MSAA was not designed to run with excessive post process shaders or multiple texture layers, let alone on multiple viewports. DCS even in 2D has at least 10 texture layers on most of the models, and most cockpits run multiple viewports, and globally, the amount of post process shaders is way up there. The performance penalty is huge on 2D, So naturally VR is more than twice as bad . TAA has it's quirks but will only get better, DLAA uses TAA + Tensor Core powered Shaders, FSR 3 ( I think DCS still uses 2.0), uses TAA + AMD's Shaders. I haven't gotten around to using DLSS -> FSR 3 Wrapper, to see if it's better than FSR2 in DCS.

right now no. main purpose of mini-mode was to allow user to manage dcs install functions w/ minimal screen space impact. Once a lot of code issues are cleaned up and I turn my attention to UI cleaning, I will be converting a lot of menu options to flow panels, which is what modules pages use, to allow dynamic adding/removing of items while maintaining their order, etc. Both Main UI and Mini UI may have size adjusted as well.

I'd Backup both Saved Games Folders \DCS.STABLE.BU\ and DCS.BETA.BU\, Update to the latest Stable once Beta is discontinued, launch DCS to let it build a new saved games folder, then copy back items you need, Specifically \Config\, and maybe \Scipts\, to begin with as that's were your settings and stored control bindings are and any customer scripts, which may or may not copy over without issue depending on USB device ID changes or binding changes, I recommend exporting controls to a file first, and try re-importing them back. Then \Mods\ and other mod directories, etc. then screenshots, and tracks etc can be easily merged, as the changes of filenames being the same in those folders are next to nil, ignore the shaders\fxo folders and let the sim re-compile them fresh.

needs to be an R in there, change their name to : Boring

I'll test again in a day or so, travelling for work.

This is the situation step by step that I'm doing:. -Launch Oculus VR, Wait for Home to load in headset. -Launch DCS, As soon as Home in Headset fades out w/ chime, I get a AMD Driver Crash Prompt. -DCS screen remains in headset, but frozen. and 1 frame every 5 seconds the position of said image would update. -C.A.D., End Process on DCS (well I use my app obviously). -Close out Oculus Home, as even after DCS Process is terminated, the image remains stuck in the headset. -Launch Oculus again, wait for headset to kill the DCS Image and reload home. -Launch DCS in VR and it loads w/o issue. Now if i close DCS, I have to repeat the process. this also occurs with every other VR app I use.

Just to test, Launch DCS in VR, when it crashes, end process on DCS and Close out Oculus, launch, close it again, then launch it and then DCS. I have this issue w/ every VP App right now, Except it's crashing AMD's driver, but only does it when I launch a VR App,

it takes more time, effort, money to remove something that's programmed into the O/S, rather than to just drop it and remove it from their store. (say it's unsupported from whatever date forward). Last time they tried to do a feature removal, it caused issues, as other features still relied on some of the libraries, lol. 99% chance, even after they say it's removed, all the files and system will remain, but MS will say it's un supported. Long after the death of Windows Media Center Edition, the files are still on my Windows 7 rig, and still work w/ a little tweaking and library registering. there's way to many users out there for MS to simply wipe it from windows, and even if they did, there's a good chance the community would develop a 3rd party app/driver to interface it with another API.

RAID And SM BUS Controller are Chipset Drivers: https://www.asus.com/us/motherboards-components/motherboards/tuf-gaming/tuf-gaming-z690-plus-wifi/helpdesk_download?model2Name=TUF-GAMING-Z690-PLUS-WIFI PCI Device can be anything from LED Controller or Onboard Audio Device, Wifi, Blutooth Controllers etc, f you're not using onboard audio (instead using a USB Headset), Disable the onboard audio in the BIOS. Same for Wifi/Blutooth. Unknown Device can be anything from a USB Device that failed, or an item connected to the system mainboard that failed. You're best option, download and install all the drivers. Remove all USB Devices Except KB and Mouse. If Errors are cleared it's one of the devices you removed, if not, it's Board I/O related. (Onboard Audio, USB Controllers, Blutooth, Wifi Etc)

As Stated, no Docs, Manual was started and paused, as during the post launch revisions, things started changing, so manual was put on hold until the changes were finished, the will be an online manual (or an embedded one, not quite sure at this point which route I want to go.)

Not currently, it was part of the old app (forcing VR Preset when Launched in VR), but received a lot of feedback/requests to remove such a forced setting. Open Notepad, put anything in the box, Save as ED Updater Utility v2.log in the path above, There was a special scenario bug that would cause exception because it was trying to write to a file that didnt exist before the function to create the file was executed. It's been adjusted internally and should make the next build.

I'm not part of the Sufa Team, please reach out to them.

DCS is an ever evolving software platform utilizing dozens of modules supported by dozens of 3rd party developers, there will always be bugs, that's just the nature of platform software. Removing the beta/release branches removes a SP/MP/Community split, and removes the need to monitor and maintain both code paths, instead, ED can focus on a singular code path, instead of developing fixes for both OB and release.

TF-30 is PW / F-14A, F110 is GE / F-14B & D That Video is a D, you're mixing 2 different engines.

At an airshow, an F-35 at max power and max acceleration doing a 8+ G turn in front of you, will cause your entire body to vibrate. The engine is huge, and the new engine is bigger, The Tomcat, had a special feeling compared to everything else because of the unique distance between the engines, regardless of A or B/D, it's still a Big Engine. A Tomcat doing a break in front of you at full burner, is significantly more powerful feeling that F/A-18s, or F-16s (which use the same engine core as the B/D). However, NOTHING, will add up to a high speed max power break of a B-1B

It's the same way with AMD Eyefinity, though it has gotten significantly better vs how it was 10 years ago, the Hot Keys made it easier to enable / disable eyefinity arrays (plus you can save multiple array profiles), I had a 1 Screen, 3 Screen, 4 Screen, and 5 screen profile set to hot keys. switching between 1 screen and the others was easier and quicker than disabling eyefinity and then disabling specific monitors. Also, as of 2019, I just use Extended monitors, and re-do a custom 3 Monitor LUA to extend across all 3 screens as a single center monitor (total horizontal resolution), then limit UI to the middle screen. the only thing that doesn't work in extended modes is forcing exclusive full screen. (it will fullscreen to middle screen only).

#Classified

honestly the only things that need to be added are Angle Adjustment from Center, Right now 3 Screens (L - C- R) Viewports automatically assume the screens are 90 Degrees Offset, You can manipulate via the dx values, but in the end it would be easier to have a UI option to set the camera angle from center, FoV as well. I ran 4-Screens for over a decade before VR took over, and still run 3 Screens every now and then.

in gaming CL14 to CL16 wont be visible.. in benchmarks... marginal.

8700G will be slower due to higher TDP and lower PBO Headroom and no VCACHE. as other have mentioned already, it's an APU with 1060ti level GPU on board, but throwing 2 full size processors on one substrate (CPU+GPU), especially when running sims like DCS, you'd hit thermal throttling significantly easily.

Ohhh, MiniDV cam microphones are about 10mm diameter, the fact that you hear crackling and static the entire time, the microphone is clearly not capable. I dont think users understand what type of microphone is needed to get clear sounds from a jet engine. Shoot, when we were recording audio samples for Forza, (cars), we had to have 4 different types of mics to record engine sounds, turbo sounds, exhaust sounds, and transmission sounds alone. A Jet engine, you need a mic that can handle high dB, as well as High Freq. Range, but also need attachments to block wind / air movement noise, etc. Also, good luck getting a F-14A or B to get modern sound equipment near those engines. 90% of the developers use the same audio source (NASA has Both PWTF30 and GEF110 audio files recorded), and just re-filter/adjust the frequency to tweak the output. However even though they were recorded with decent mics, they were recorded in an enclosed room / hanger, so there is sufficient reverb noise. this is where LFE comes in, We need to wear vests with radial rumbles in it, so when ABs light, the LFE is translated to the vest rumble simulating chest cavity rumble.

We are all thinking it.. We need this campaign:

The TF30's on most youtube videos are sourced from VHS LP Tapes, If you prefer that, goto your audio control panel in windows and cut the audio freq. to sub 24Khz sample rate.

Considering the MFDs from Front Pit and Back Pit are likely cloned and not independent, you have 1 set rendering above the other.