SkateZilla

For the record, they don't really have the same level of Manufacturer's Licenses/permissions as ED/DCS 3RD Party's. *If they have any at all, as all they are using is the visual representation, which IIRC does not require a license. But that series of titles, NONE of the systems are modeled, they have a generic underlying system that is adjusted per aircraft the user is flying, some displays look visually correct but they are simply basic representations of the data the underlying generic engine is providing. Their Content is meant right where it is, in a visually over saturated, cinematic style camera, heavily filtered, arcade game. Remove those filters, and the content would not look the same (I've seen many of the models RAW, w/o the graphics engine filters, they are nothing close to anything ED or 3rd Parties have put out in the last 10 years.). As for Story / Campaigns, again, not the DCS Path, they are fictional out of the ballpark cinematic scenarios...

iirc they were changing the product pages and the videos were having issues..

it wont work with the updater correct as it's a command arugment for the DCS EXE, which is why my instructions say DCS.exe, you can change the autoupdate cfg, to add the --force_xxxxx_vr to the end of the Run \Bin\DCS.exe Line. Inside the quotes and it *should* work, but I havent tried it lately.

--force_enable/disable_VR Overrides the [VR][Enabled]=True/False Setting in your options Easiest way is to make 2 shortcuts to DCS.exe, VR Checked/Unchecked wont matter, have one shortcut --force_enable_VR (plus any other VR Arguments for API), name it DCS World VR, have the second shortcut --force_disable_VR, name it DCS World NonVR.

The hook system is already there, you just have no land based arresting systems in DCS,. Unless it was disabled to solve landing Vipers on carriers issue.,

More threads isn't always better.

If they fix the VCache heat and cost issue, they'll likely just start building them with vcache dies inbetween the 2 CCX's allowing both CCX's access to the entire pool of L3. The new threadripper is 64c/128t at 350w TDP (uses about 600w overclocked w/ PBO) Cores isn't the problem, heat dissipation is, the smaller everything gets, the less interface material there is to move the heat off of the CPU. ie, the ThreadRipper 64c Chip, is huge, and the heatspreader is around 4x the size of the 7900 series CPUs, The thing hits 5 GHz on 64 Cores while remaining under 70°C.

Intel has their Cores in Unified groups as well, it's not a CCX issue. AMD's issue is X3D Cache is only on one CCX, so when a program is moved to the other CCX, performance suffers. Non V-Cache CPUs the performance is the same regardless of the CCX the thread is placed on. It's Multiple CCXs and MCDs on an Infinity Fabric on a single substrate package. CCX's will not get larger than 8 cores anytime soon due to optimal yield size being 8 cores, as all 8 Cores can architecturally be linked in processing, moving to more cores in the CCX will drastically increase the size of the CCX. Windows 11 is supposed to recognize the processor and limit gaming to a single CCX to decrease latency and cache jumping.

One of the first 3 stages is being returned as valid folder. Stage 1, Check for DCS_variant.txt, check default folder path for variant in DCS_variant.txt, if Folder Path exists Set as Selected SG Path. Stage 2, if dcs_variant is not detected or path it points to does not exist, generate path based on branch (release or openbeta), if Folder Path exists set as Selected SG Path Stage 3, if Branch path does not exist, use User Set Path, if Folder Path exists set as Selected SG Path Stage 4, if none of the Paths in Stage 1, 2, or 3 exist, set at "Not Configured" and bypass scans. Attach the App's Log File, it will tell me what's going on.

Launch Button on the top will launch DCS with the settings present in the .lua So Under [VR] if it's set to Enabled = True then it will launch w/ VR On, Launch VR On, will launch DCS and Force VR On regardless of that setting. Launch VR Off, will launch DCS in 2D Regardless of that setting.

5800X3D or 5700X3D, 5600X3D was a microcenter exclusive, but in reviews was already bottlenecking due to less cores and lower TDP. the 7K Series, don't go higher than the 7800X3D, because then you'll have two CCD's one w/ VCACHE, one without, and you;ll have to disable the 2nd CCX to keep the Vchache cores from dumping work to the other CCX.

Create a Repository Folder, ie Drive:\\DCS LIVERIES\ Create Aircraft folder within it. ie Drive:\\DCS LIVERIES\FA-18C_hornet\ Place Livery folder w/ description.lua and textures in that folder. ie Drive:\\DCS LIVERIES\FA-18C_hornet\HORNET_TEST_LIVERY\ Open DCS MAIN FOLDER \ CONFIG \ MODEL VIEWER \ autoexec.lua Add the line below to the LUA just before the "PRINT/DONE" Lines. ~Line 84: mount_vfs_liveries_path ("<path to main liveries folder>") (obviously Drive = Driver Letter) ie: mount_vfs_liveries_path ("Drive:\\DCS _LIVERIES") print("done") print("----------------------------------------------------------------") Open Model Viewer, Load your EDM, and Select your Livery.

in this situation, The IRS is taking as much as I give, as I'll end the current pay period with 80+ hours of OT and Holiday Pay... lol.

This was found and fixed internally a few weeks back. I'll let it slip that I've also re-wrote ext apps launch function, to allow user to change the order the apps launch, before or after the sim, and the delay time in ms between app launches, etc. A lot of cleaning up and stuff needs to be done before the next pub release, with me working 80+ hr work weeks, I haven't had time to productively code anything.

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.