SkateZilla

They are still on the first page on the left. Click on the "?" Icon and click Online Manual.

The lines to disable the radar are standard environment.system time request lines (getSystemTimeAsFileTime), nothing a AV would flag. if the file was deleted by the AV previously, it wouldn't flag after, if the file was "Patched" by the AV it wouldnt flag, nor load the library when DCS Launches. Attach your DCS.Log, But I can almost garauntee your AV Suite nuked the file or tried to patch it, in which case it fails the DRM check and isnt loaded by DCS which causes modules not to load.

Logged: EXT_SCRIPTS_2.0.0.38 Fixed in Version 2.0.0.39 Apologies, that was a goof up on my end, When I re-wrote external apps, the custom scripts part was left off the function order, as it used to be a sub function of external apps. If no other major issues come up, I'll release a update/hotfix this week.

SteamVR is the default when launching DCS:VR in Single Threaded Mode, as OpenXR requires Multi-Threaded Mode. Should be running in MT mode regardless as many things simply are coded for MT Mode only and do not work on ST Mode, ST Mode is only retained for Bug Checking/Safe Mode use at this point.

The Flight Models are the same, however, some of the advanced systems are not available on the FCS Version. FCS: F-5E-3_FC is equivalent to DCS: F-5E w/ some of the Stability Channels turned off performance wise.

The tank is the F-5A/B 150 Gallon used by Spanish Air Force and a few export customers. This particular aircraft is ROCAF, ROCAF Initially Purchased F-5A/B's with the Export tanks. Later Taiwan Built E/Fs under license w/ modifications (Closer to F-5EM Standards, and a few elements from the F-20 Program). They retained the 150 Gallon tanks from their initial F-5A/B Purchase as they are compatible with the F-5E's pylon.

The radar disabling code was fixed in the last patch and unrelated, if your DCS Folder isnt excempt from RealTimeScan/Protection, your AV will continue to put DLLs in quarantine or delete them.

there are a few things the ED Launcher does better. For me specifically, I use my app to manage all my installs (release and testing, as well as servers). As well as debug / testing purposes (Launching w/ custom arguments / or autoexec settings etc). But I still use ED's launcher for tweaking a few settings sometimes. ED also plans to Expand the launcher, so there's likely a lot of new stuff coming to it. For Example, LUA Parsing of the Options.lua. You can still manage all the App Profiles as before, and launch the launcher, my app will activate the profile, and you can edit within ED's Launcher. I'm not 100% certain i've debugged the LUA Parsing for specific localizations yet, and there's funky behavior when specific values are changed, despite putting version tables for those strings, the LUA Parser sometimes has a stroke. Ie, I sometimes get errors w/ RainDrops Quality, as w/ this latest version, it's now Off, Low, High, instead of On/Off. DCS would auto-set low for anyone that had the option checked prior, so the app tries to do the same, and sometimes it confuses it self.

The app doesn't re-configure windows to use different folders for User Profile, The option is there to point the app to another path for storing the app's data only.

Right now I'm remastering the Wingtanks and 150 Gallon tanks, I have no plans to do antennae or refueling probe. But from what I saw it was also self contained. I May go a similar path, with having a separate F-5E / F-5A Declared, import the base F-5E then declare an sub variant, and add the changes to that variant..

Added to first post. Forgot to mention, there is a online manual, in the help icon on the top right, I'm slowly building the manual sections at a time.

Final Changelog for next public version (sorted oldest items first): Rar File Added to First Post.

By default in the current Stable build, If FC3 is installed and Authorized, it disables the individual aircraft. It has been this way since the beginning.

The community is hilarious, No News/Announcements wasn't well received, So ED started tentatively announcing things, and then whenever there is a delay, people say to just stop announcing things. it's like going full circle. Does someone wanna go through the last year of patch announcements and count how many were delayed, bet it's under 10%. I've seen the Post by Chizh that leads one to believe this, and I'm pretty sure everyone is missing context and mis-interpreting his post,

Default ones are in: \DCS World\Config\MonitorSetup\1Camera.lua You should make a Custom profile in: \Saved Games\DCS.<branch>\Config\MonitorSetup\ Rename it to something like 1Camera-VR+Screens.lua then change the name in the LUA as well. Edit the height/width Values to match you total display area, Or, Paste into notepad++, edit what you need, then save into the Saved Games\DCS.<branch>\Config\MonitorSetup\ Folder, Launch DCS, Check the "Mirror Use DCS Resolution", then Choose this monitor Profile, Relaunch DCS.: _ = function(p) return p; end; name = _('VR+MFDS'); Description = 'Left/Right on the monitor, Mainviewport in VR Headset' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = <pixel position of left edge of MFD>; y = <pixel position of top edge of MFD>; width = <pixel width resolution of MFD>; height = <pixel height resolution of MFD>; } RIGHT_MFCD = { x = <pixel position of left edge of MFD>; y = <pixel position of top edge of MFD>; width = <pixel width resolution of MFD>; height = <pixel height resolution of MFD>; } VR_allow_MFD_out_of_HMD = true UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

You can export MFD's to Separate screens in VR By: A. Adding "VR_allow_MFD_out_of_HMD = true" to monitors.lua B. Checking the box saying "Use DCS System Resolution" in the VR settings in DCS C. Set System Resolution the Correct resolution (ie, same res you would have if you were running 2D. C. Setting the Coordinates for the MFD Windows.

Just a quick blurbl, The Wintip tanks are undergoing a re-master pass, -Revamped and re-shaped the 3D Model. (the shape was adjusted, and re-smoothed, some parts were re-built). -Revamped the UVW Coordinate Mapping. (I actually re-did the unwrapping twice, because the first pass had some issues.) -Merged all textures into a single texture file. (Glass, body, illumination etc are all one single 4096 Base texture). -Converted to use the latest PBR Elements. (Glass, Chrome, Metals, Oil, AO, etc) -Revamped template w/ more detail / stencils. ( A LOT MORE! ) -Oh, And Let there be Light. *(Tweaked to be minimal in the day, but visible at night) Once the PTB 50 Tanks are done, I will start on 125 Gallon 2 and 3 Wing Tanks as well as Formation Light Equipped wing tanks. -Wing tanks will have standard and Formation light equipped versions in the loadout, unfortunately I haven't found a way to link weapon animations to model animation state, so the standard will have lighting always on *(WIP Images below), and the Formation equipped versions will have formation lights always on. *(If I find a way to pass the aircraft argument state from the aircraft to the weapon and able to use that to set the weapon arguments I will integrate such function. * pretty sure it's possible, but I just haven't gone down the LUA rabbit hole of Getting aircraft states and passing it to an externally attached model. Like prev. versions, this will be a self contained object mod, dropped into SG Folder, and the user simply add's the loadout lines to the core F-5E LUA. T-38 Community Mod compatibility is not yet determined, it will depend on whether or not the T-38A has wingtip pylons to attach items.

Resolution = Viewport Window Size, Minus UI windows that are docked. The issue your seeing is even with 4X MSAA Set in the options, there's still a lot of jaggies,

You're GPU is being removed from your system either due to driver Timeout or Driver crash recovery. Reason: DXGI_ERROR_DEVICE_REMOVED, DXGI_ERROR_DEVICE_HUNG

It's a JSON Parser Error, on Line 1 of the app because the JSON Parser DLL is missing. Also which version is this? the DLL should be embedded into the EXE in the latest public versions. As well, the Main Form is not Form1_Load, nor is the Folder Scan Function name "FolderScanAndVerify" in the new one. It seems like you are running Pre v2.0 versions.

Undervolting is your friend. I dropped 19°C and gain 20% clocks/performance by under volting my brothers 7900XTX, also dropped roughly 45W load.

Now... it wasn't broken 4 days ago, and a patch from ED didn't break it either.

Considering the EDM Plugin was last updated in May... I think support for 3D Suites has shifted. But If you need some help, I'm 99% sure I'm on the A4 discord, you can message me there. You may have to Ping me, as I'm in dozens of Discords.

EARLY . ACCESS .