SkateZilla

Check \Saved Games\DCS<branch>\Config\Presets\Default\ This folder should be empty, it's used to store the default options.lua when a preset is in use, and the file is moved back by the app when DCS Closes.

Nobody wants to sort through thousands of un-named or unsorted layers. Disagree if you want to, but templates are usually released once the artist finalizes them, as in no more planned changes, or pending bug fixes on the 3d Model. Then the layers will be named, merged, sorted, etc for deployment to other artists. Trust me, I have PSDs for my models that are literally thousands of unnamed layers.

Most of the time, Development PSD Files aren't always deployment ready. There's a lot more that goes on than simply Zipping a file.

Considering the extend HB goes with coding AI and systems, they likely could do their own system/interface for the carrier. As things developed for the SC may not translate to earlier Carriers.

Exception on startup may clear the settings file. I'm looking into that separately, You may be able to TaskManager End Process, so it doesnt save/edit the settings store file and then re-launch the app. Also Can you paste the error message as text so I can translate it, but it looks like it was unable to write or access the log file. On Another note, if anyone is having issues w/ dcs_mt_manifests and my app after the OB update please post logs, I have a few reports but I am unable to re-produce. Yeah the initial Parser Changes didn't fix the issue, I've since modified the parser further and testing some other things internally, hopefully the next build will address is completely.

This should be in the Heatblur section, since the Forrestal is their carrier.

With Block III, the USN only ordered Es and is only Rebuilding Es to Block III Spec at the Depo. F's are being mothballed for parts for the Growlers if not converted to Block III Spec Growlers. You dont really need a WSO Anymore w/ Block III.

Note: Adding the option to the optionsdb.lua will only work as long as the settings for that value are in the shadows.lua and shader files. I mean if you wanted to you can just change the parameters of the High Block to match the ultra block. Change: { --high 4096, {0.02, 25.0, 100.0, 400.0, 1500.0, 7000}, {0.02, 2.5, 25.0, 250.0, 1500.0, 7000} }, To: { --ultra 8192, {0.02, 25.0, 100.0, 500.0, 2000.0, 7000}, {0.02, 2.5, 25.0, 300.0, 2000.0, 7000} }, And further info, you can simply create your own settings: { --referencename 2048, -- size of shadowmap {0, 0, 0.02, 20.0, 70.0, 7000}, -- split distances outside {0, 0, 0.02, 2.0, 20.0, 7000} -- split distances in cockpit },

SSAA Can be done in both AMD and nVidia's Graphics panel automatically.

Did you set the correct VR API in the Advanced Launch Options Tab? That's an odd shift, since the track bar is simply the IPD Vale x 10 (63.5 = 635), since track bar control doesn't allow decimal places, and then converted back by taking track bar vale of 635 and dividing my 10 to get 63.5

I have recently found a compile error where Visual Studio changed all the parser values from "true/false" to "True/False", which causes 80%~ of the values to not load or save correctly because they are case sensitive, I don't know when VS changed them all, but I'm working through fixing them all as I go through the entire save/load/import/compare functions to add some additional parameters to each value. there may also be parser save issues in relation to specific locale's still as I'm still seeing values saved w/ a "," instead of a ".", I'm also correcting that. What Value Behavior are you seeing? as I've been adjusting mine frequently with no problems. Also if "Custom IPD" is not enabled, that value does nothing. Right now I'm just swamped w/ Primary job. 120 hr work weeks and all that.

Apologies I dont handle DCS Crashes.

AH-64 was in plans in 2006 (Originally an A), No one ever said that it wasnt happening, there was posts about the later blocks, some weapons and the -E Variant being a no go.

Who said that about the AH-64? Also do you understand the AH-64D Modelled in DCS isn't even the more recent D Block? Eventually, Testing Sqns always have stuff way before the capability is deployed to the fleet, and manuals are made. Looking at at least 1 year if it passes quals before it's deployed to fleet in a OFP Update and Manual.

We will, that's the thread topic.

if mission designer were to put them in the same mission then that's on them, But realistically naval F-4s and Super Hornets never Flew at the same time, nor did half of the aircraft we have in DCS now, Basing selection off their board call is not a smart business decision. As for Bridle Launched Aircraft, you cant expect a developer to make engine changes based on a 3rd party mod, DCS can support Bridles just fine, the 3rd Party team can integrate it on their own if they wanted.

F-4's and F/A-18 Lot 23+ Never Flew at the same time, so Re-using the Rhino call doesnt affect operations.

Thou gent hast 555 posts since august 2006, th'ref're gent is not new Blame it on auto correct, that's what I do and 99% of the time it's actually true.

this seems more of a System Software/Hardware issue, with USB Polling and latency causing the FPS Stutters you're seeing.. 60 FPS is 1:2 pulldown from the TrackIR's sampling rate, w/ Native being 120Hz, which is why those FPS look the best, If TrackIR is Polling at 120Hz and your FPS is some random low number like 37, then there's going to be latency introduced due to the pulldown and sync, the same happens in VR, TrackIR has yet to update their software to be asynchronous to the GPU Rendering rate. NaturalPoint (is it OptiTrack?) has been pretty much sitting comfortable with trackIR4 and 5 and hasnt done anything to update them to work with today's GPUs.

My thoughts and opinions are of my own, and have no affiliation w/ ED or their Business decisions. But I did give it a re-post.

There is no HB A-4, ...

You'll have partial functionality for steam, Launch Functions should still work, Adv. Launch Functions should mostly work. Anything dealing with the Updating, Repairing, Cleaning or Module Management will not work. as "DCS_Updater.exe" is not part of Steam Distribution.

there is no Fighter / Attack - 18G

you can use them locally on the client PC, VR or Screen regardless, if you want them networked, then OBS -> Set Region, Stream to networked screen.

It fixed in the last patch, before that it didnt work so I did have the app launch it. Next app update will launch MT version if above Version # for MT MV working.