SkateZilla

it should override all.

Sorry Guys. Try options.graphics.objects I think i had them reversed by accident.

please don't compare the two, using MSFS20 as an argument for anything DCS related doesn't mean anything. FS20 on Xbox Series X is Physics and Graphically Handicapped compared to the PC Version, plus w/ DX12, they do not have draw call overhead.

it cannot (fluidly), I know modders that modded their Xbox Series X to run Windows 11, and DCS runs at like 15 FPS on the APU, and performance degrades as the APU begins to thermal thottle.

Likely be better to expand that to a "My Hanger" Section... similar to "My Garage" in most racing sims.

The PS5 (And the Xbox Ones for that matter) doesn't have the O/S or the Hardware power to run DCS.

The PCI_E2 Slot should have the same bandwidth as the PCI_E1 Slot. (Unless your Manual specificly states its x8, x4, x2 etc), but most Gaming Boards tend to have both Full Slots at x16. As for Setting up in VR. 99% of the Players get so focused on the FPS Number, and honestly that's the fatal flaw with everyone in VR. While the FPS is key in determining whether or not there's going to be a sync pull down. They should be adjusting settings and doing test runs based on gameplay smoothness. Honestly, I'd say Ignore FPS, as it can be mis-leading, especially when the Sync Pulldown is applied.

The current version should remember the build that was last selected, As for preset, it should set the preset that was active in the event of an app crash and restore while DCS is running still, But as far as preset between builds, it wont, there's too many variables with files moving/missing to force that behavior.

The Lot before the IIAF Order was IRST, but they were replaced or removed/capped off in the fleet as they didnt perform. But in the Image it's clearly TCS, as IRST has the Eyeball Lens and not the Flat Lens.

This is a Demonstrator Airframe, flown over the U.S. to demonstrate the TCS as an options etc. TCS was removed before it was delivered, as IIAF Declined that option. The only reason it's 100% Clean is they were also demonstrating speed, etc. Tail # 3863 is the only Tomcat w/ TCS and IIAF Markings

the syntax might be wrong, I'll have to check it when I'm at home.

Every patch it will reset it back, having it in the autoexec.cfg will retain it after every update/clean/repair.

you know you can add this to autoexec.cfg in your /Saved Games/DCS/Config/ Folder? graphics.options.objects = {3000, 80000}

USN Cancelled it before receiving, IIRC. Unit was originally supposed to be part of Block II upgrades, but USN Delayed it to Block III to divert funds to the F-35 Program. FPU-13 Fuel Tank, Fitted with AN/ASG-34. Budget cuts in the Hornet Program, removed a lot of Block III Extras. IIRC Boeing is still developing the pod for potentional FMS Market orders, and if the USN Changes their mind again.

You completely missed the entire 5 pages where people were assuming ED or 3rd Party could mix and match Early and Later blocks to have specific features, Which is where my replies were directed. But as Stated w/ Lot 25, it's not just AESA that is classified, core components of that lot, are still classified, so it would be Lot 24 or Earlier LRIP Lots.

The Super Hornet was to get the IRST Block II is part of Super Hornet Block III, and is a Fuel tank fitter w/ electronics and a IRST Head, not the legion pod.

I get 45~ FPS on a MSi 7970 Lightning w/ DCS OB, And that's with a few things on High, If I Drop everything to low, pretty sure 60 FPS is possible.

Not exactly Breaking news, Block III's didn't sell on FMS Market like they thought they would, USN was only using them as a stop gap for F-35Cs to get Capacity, In 15 Years the roles will shift, F-35C will be the "Cheap Fighter" and the NGAD will be the new expensive one on the deck. E/F Lines are shutting down, Growler Lines will remain open as they still have production orders to fill. Staff will move to T-7A, and F_15EX Production, as well as re-locate if needed to Cecil to maintain and upgrade the current Super Hornet Fleet. The navy isnt retiring the Superhornets until at least 2035, and those will be the Block IIs that didnt get upgraded to Block III at Cecil. The Upgrade pipeline will remain active for a while at Cecil, as Block IIs to Block III Upgrades arent estimated to be done until 2033. The funny part is, the F-35 Cost overruns, is what costs the SUper Hornet the EPEs (or their delay), the CFTs, the EWP, the IRST Pod etc. the Only block III Extra feature to make the USN Cut was the NGJ, but even that barely made it through and still hasnt even finished prototyping, and has already changed names,.

https://www.techpowerup.com/305181/amds-reviewers-guide-for-the-ryzen-9-7950x3d-leaks

The Slide shows L2 + L3 cache.

Im unable to re-produce this on OB or Stable MV, J11 Opens and Generate Button generates fine. Do you get a File Save Dialog when you click the button or is it an instant crash as soon as button is clicked, Judging by log, if no dialog pops up, it looks like an error w/ the QT Platform files/dlls. Might want to try a repair to restore or clean those files.

The Mod is defining it's own missile w/ the same name and different texture file names. They are conflicting w/ each other. Since the MF.1EE and it's Ordinance are Part of DCSW Core, the Sufa Team will need to update their mod to fix the conflict.

I mean, if you want some help or pointers... all you gotta do is ask, Assuming your source models are the File404 models, it shouldn't be that hard. If you want an example, I will share an image, but otherwise I dont want to spam my renders in your thread out of respect for the team.

This issue is caused by a /Bin/EXE or DLL Missing Version Info, For Release/OpenBeta it's most likely QWindows.dll The version issues have been fixed internally for the next version.

Well, The HOL is a custom programming Language Boeing uses on the Super Hornets, HOL Language by itself isn't Classified, like C#, C+ Pyton, etc etc. What is Classified is the HOL Based SCS Operating Systems in the Super Hornet Starting with SCS-H10 (and any Evaluation versions before deployment). Since HOL-SCS is still Classified, good luck getting any Engineering or Systems manuals for any Block that uses HOL and SCS-H10+. So you wont even be able to "Fake" the appearance, as there are no Classified Elements in the Publicly available Manuals, the public NATOPs covers LRIP BuNo 165533 thru most of Lot 24, there are some late Lot 24 Changes that aren't present in that manual, let alone anything Lot 25+, the only manual with Lot 25+ info is the Growler Natop, but even that manual only has limited information, as it's based of 166855, which was the first E/A-18 Test Aircraft after the Modified F/A-18E BuNo 165779 which was a Lot 23 Aircrat. 90% of the Growler NATOPs is copy/paste from the E/F NATOPs as it's mostly procedures etc, the only difference is procedures w/ the Jamming Equipment, none of the AESA or Classified items are in that manual. So there's nothing to even base a "Faked Out" system on. So while you can Fake out a General Appearance of a Super Hornet's systems, you wont be able to accurately simulate the other components that are still classified. (ACS, AESA, A bunch of smaller radio and Countermeasure systems, etc etc etc). While Even F/A-18C is a Mis-Match of OFPs, it conforms to being a Pre-HOL SCS-2x System.. The same configuration most of the C Hornets had ED did not mix SCS-2x and SCS-Hxx Features.