SkateZilla

Pretty sure there are pre-requirements, you cant just email and be like I want all the Manuals for F/A-18C Lots 20 through 22 and they reply back with PDF Links.

Boeing licensing doesn't have anything to do with me. But all Lot 20 manuals are available without restriction (except a few things.) The same cannot be said for the Super Hornet.

Current temps of the GPU hotspot doesnt change the outcome. Lower temps just mean they fixed the TIM and Concaved Die issue causing the heat to not transfer to the heatsink. They still pull 300-400+ watts depending on the OC, the lower temps just mean that it is transferred to the Heatsink and blown into the system air or exhausted out the back more efficiently. I've seen users that run 2 gaming PC's in the same room w/ 4090s, when gaming, if the door is closed, room temp rises by 4-7° in the spring/fall, more in the summer when the air is already warm, and fighting the outside heat. There's also the issue of the 12VHPWR failures still.

Just a quick update, and Apologies if it sounds a bit brash, there are external factors involved at the moment: - I Am working on adding a few under the hood things to the app. *( to further help w/ tracking issues ). - I Am also integrating a few things that aren't public yet. *( and Need time to test internally ). - I Am tracking the Thread issue, narrowed it down to the source and testing work arounds, if they don't yield results I am looking for then I'll revert the thread changes I integrated for the last public build. - I Have a few projects that are Higher Priority. ( As Stated Before in this thread and other media platforms ). - I Am also enduring a family medical crisis, which has taken up all free time at the moment, and greatly impacted personal things. *( The external factor mentioned above. ) - There is no need to repeat post on my profile, send me PMs, or Ping / Tag me etc. (whether here or other media platforms), repeatedly asking for updates, this is a hobby/free time project and not under any license or user agreements to which I owe any updates, material or verbal. Updates will be posted when I have updates to give.

In the Summer, My PC's Exhaust is vented outside :-). Keeps the AC from constantly kicking on, In the Winter, My PC's Exhaust is vented into the room, and keeps it warmer in the fall/spring so I rarely run the heater. ( I grew up in Niagara Falls, 40-50 Degrees we get here in the winter is tank top weather for me.)

and a nuclear reactor for power and a contained section of vacuum sub space to extract the heat to.

Trying to use Explicit MGPU in Vulkan w/ an older GPU will not yield the benefits you think it will. - The Driver for that GPU Needs to Still Support the Version of Vulkan you are running on, I don't know about you, but my "old" GPUs are in long term support, and their last set of drivers still haven't added any recent Vulkan capability, AMD's Legacy Drivers for anything Pre RX 5xxx would not work correctly, if at all. - Mixed Explicit MGPU also does not directly share data, So if you run a AMD RX6900XT and a RTX 3080, then Vulkan MGPU will not put them in the same group, and thus, for every function requires a trip through the CPU to process and convert data, which causes latency and performance issues. Same for if you are Running a RX6900XT and a RX6800XT, if the GPUs do not Explicitly match, don't bother trying.

Vulkan Dual GPU is not the same as Crossfire or SLi.

So, to nix that urban legend. Launch DCS Load a Decent sized Mission, Note the FPS, Now Restart the Mission, Alt Tab out, and Tell your Virus Scanner to Scan the DCS Folder at the same time. The Assumption that Active Virus scans don't hit performance has already been proven false by EVERY YouTuber/OverClocker/Pro-Gamer. The RealTime Protection scans literally every file as it's being accessed, every item as it's being moved from one memory address to another, every running process, including 3rd party processes for addon UI things *(* ie HeatBlur modules), every incoming packet coming in from a MP Server,... eeevverrryyy thaaannngg. In smaller missions w/ less stuff being accessed, you might not notice the hit, but it's measurably there, in MP on the other hand, w/ large missions, the impact is real.

Testers have raised this issue internally. Both the flickering and the "Frosting" effect of the overpowered reflections on the canopy. please keep in mind Newy and Ben are very busy individuals and may not have time to respond to every mention/tag.

The HUD being too large like that is usually a symptom of a bad "Views.lua" file

There's default shortcuts directly to the DCS.exe, it's not required to launch DCS from the Updater. Bypassing it does nothing to the DCS.exe process or memory address.

can bet his autoupdate.cfg points to the the ST dcs.exe

It's not hardcoded, it's the 2nd to the last line in the autoupdate.cfg "launch": "bin-mt/DCS.exe" But Like I said, I launch DCS.exe directly in either mode. I only use DCS_Updater to update. There is no repercussions to launching dcs.exe directly. Like I said, the only difference would be if there is launch arguments in the shortcut for DCS, that are not present when launching the .exe directly, in which case it's User Error / Bad Shortcut, not Circumventing Updater. I haven't launched DCS through the Updater.exe in over 5 years, I've always launched dcs.exe directly, or if I want to update dcs_updater.exe directly w/ command line to only update, then close. So we'd need to see logs to see what parameters they are launching with in both instances, because the MAP issue is related to ST, as some of the functions were re-coded for UI / MT Performance.

please attach dcs.log files for both instances. run DCS directly, get into mission goto map, exit, attach dcs.log run Updater click later, get into mission goto map, exit, attach dcs.log.

A. Clicking "Later" still launches the DCS.exe from Bin-MT\. B. I repeated the process of clicking later, and DCS Launched in MT Mode, and the Map is fine. C. Users reporting this issue are users that are launching directly into ST Mode using modified shortcuts and/or command line arguments.. The Updater Launches, Checks the Server Version #, Prompts for Updates and either applies them or doesnt, clicking "Later" Launches the DCS.exe and Exits DCS_Updater, Launching Updater, Clicking Later, should not have any affect on DCS.exe itself, THE ONLY time you would see a difference, is if your DCS.exe shortcut has command line arguments added to the file path, because clicking "Later" does not populate the arguments from your shortcut.

Duplicate post.

Going back to ST isn't the solution, If users have an issue with MT performance, logs and data are needed to pinpoint the issue, Falling back to ST is not going to fix the issue, plus falling back to ST is likely not even a valid solution and more of a placebo. as most of the new under the hood systems are coded for MT, falling back to ST disables a mess of under the hood things, so the increase is FPS or removal of latency is likely a result of a lot of things being disabled due to requiring MT binaries. So in the end, your trading the FPS/Latency for disabled systems and a bunch of missing under the hood instructions, likely causing stability issues.

that solution was known for over 2 months, that solution was known for over 2 months,

nope.

I've been an advocate for replacing the old Flanker/LockOn Models w/ updated versions based off the new models.

So far that's the only shot that's available.

ST has long been depreciated and only left in as a Failsafe/bug check function, for a while now the default shortcuts and command lines from Updater have pointed to MT, the only way you'd be consistently launching ST is if you manually made a shortcut to it.

I have no disclosable information regarding an ED Update, I have things for this mod I need to finish, however I have other projects I am currently working on / with teams that have tighter deadlines + complicated issues with non DCS related life events going on.

This happens when there is a broken link to the flight model, mostly from past edits changing FM Names in the config.lua etc. Pretty sure GD released an update that fixes everything without a need to edit files.