MadKreator

1st pic , is without the reshade mask, my f-15e profile, with lighting set in night mode.. screens basically invisible..(in person you can barely make them out) the 2nd is the same settings but with the reshade mask running Then A-10c at night, in night mode also. World of difference! ( I added a Levels filter too along with tone map to get a little more tweaking) I did it the way he did in this video

I did this using helios, took one big screenshot while dcs was running ( so it showed the viewports) , colored the whole dcs screen white and the whole lower part, where the helios monitor is, black. Helios ( I know this isn’t the discussion) always places the aircraft virtual cockpit on top of everything else running, so it only affects the viewports rendered behind the cockpit. Works like a charm on all aircraft. I would say just play with the masks. Wherever it’s black, reshade will apply the chosen filters wherever it’s white, it wont. Having all the monitors in a line in windows probably takes some pain away. sorry @idenwen( the world thanks you for figuring this out btw!) , meant to reply to @Darkdiz

Sounds like great updates to it. I would still like to see an option to re-am before refuel, or to just pick one or the other easily, for certain scenarios.. just personal preference Excited for the fusing features either way!

Exporting has its downfalls too. Yes, of course it’s just the raw data from the viewports so no smudges or anything, but DCS exports are inherently much dimmer than the in-cockpit counterpart. Especially in night lighting mode, in the f-15 they pretty much disappear completely ( this is on ED’s side not RB’s though), however that can be circumvented using reshade UIMask to add filters to them and significantly increase the brightness of them. I’ve been using exported displays for a long time, however I do agree that a lot of modules are a bit overkill on things like fingerprints on displays and scratches on canopies. It would be nice if those things were dialed back a bit.

It’s been a while now (3+ years). All I had was the original Orion F-18 throttle (currently VKB STECS) so light syncing didn’t bug me. It’s not like it was the worst thing ever but I did notice performance benefits after even just commenting it. However I wouldn’t have deemed it “unplayable” by any means. Glad to hear they’ve optimized it since then! I do like WinWing equipment. These days Helios is priority for me. It gets the number one spot in the export.lua always I think it’s to be expected that any sort of pilings up of programs in the export.lua will need some tuning on most systems. Helios can be a massive resource hog itself. I’ve been lucky and it runs well for me but I’ve seen many users struggle to get the performance they want. I would imagine it’s the same with WW, Tacview, DCS-UFC, DCS-BIOS, Streamdeck etc. Anything that is really pushing a lot of information back and forth.

WinWings scripts in the export.lua always caused performance issues on my system (when I first used WW)… Unless anyone really NEEDS simappro, best to scrap it and delete the lines in the export.lua

I switched mine to 3.5.1 a few days ago. Seemed to improve the ghosting a bit, didn’t notice much in the performance range. Surprised it didn’t get changed, took about 3 minutes total to swap out… I still stick with MSAA though, just wanted to test the DLSS ver.

Is it just me, or is the cockpit / camera shake (in 2D) way excessive? I get that planes shake under high G/ AOA etc, but the f-15c seems to get massive shake ( I dare say “unplayable”-ish) with even the slightest bit more than the smallest sick movements. Much more than any other aircraft in DCS. * I haven’t flown an fc3 in years, just hopped in the to see the graphical updates and was kind of gassed at how bad the shake is in the f-15c.

I figured it wasn’t the be all end all fix like the video claimed lol It seemed to work for me from free flight to medium/ heavy missions. Now I will say, I haven’t loaded up a dense MP server or heavy liberation mission( most of my flying is testing and developing Helios stuff, not too much fun flying). I will have to try your fix on top for fun ( if I can figure it out) just to see the results. A few months ago @BIGNEWY posted a lua file (mt.lua) to add to dcs saved games in the config folder that was some help for MT. Idk if its still valid, or if that change made it in permanently.. On my side that file seemed to help distribute the load better across cores. I was getting most activity on only a few cores( 8-11 or something). After adding that lua I have activity on most all 24 cores with the densely packed original 4 distributed more evenly across the top 8 or 12 or so. * I should add, by my own volition, I do keep DCS capped at 60 fps. 1- just to give it overhead as I feel 60 fps is ample for a flightsim, 2- trackir seems to be smoother at that fps cap, 3- Helios runs smoothest in that area too…. Obviously I’m running 2d. Haven’t fired up VR in a long long time.

@Lixma 06 Adding dcs exe( both ST and MT), saved games folder, track ir, srs, helios( everything dcs related basically) as exceptions in windows defender, really smoothed out all of my stutters. I tried affinity and messing with cores with no noticeable improvement ( actually all that did was increase load times for me). But after excluding anything DCS related, it now runs smooth as glass too, not a burble or micro stutter to be found. Just another idea.

Did the save game state/ save mid mission (not sure what to call it), make it in todays patch? Haven’t had a chance to try it out yet. Downloaded then had to go work. * read the patch notes , just didn’t know if it slid in under the radar

I have a pretty high end system and still had the stutters, albeit not terrible. After doing all of the windows defender exclusions, dcs is smooth as glass as well as track IR. Memory upgrade will help. I’d go at minimum to 32 gigs. 64 if your mobo supports it and of course if the price is right. I would also look into doing the 32 gig pagefile thing too. I have 64 gigs and dcs will eat well into the 50’s on a big mission. DCS will use what it needs based on what you have.

I will 100% agree with this. Playing Reflected’s p-47 campaign it is hard enough to keep up with the rest if the flight, but as soon as the AI starts climbing they just pull away with seemingly no loss in power and it takes every bit of distance across the Channel and beyond to catch up. Even with perfect manifold pressure, boost, max prop speed, perfect rudder trim and well tuned mixture…here I am with no chance of keeping up with them lol

DLSS is prob great for lower end systems that struggle a bit. I replaced the DLSS DLL 3.5 with 3.5.1 earlier today ( that I saw in some video) and it seemed to improve ghosting a bit but nothing truly spectacular. Performance improvement fps-wise, sure, but the graphical degradation is very noticeable to me on a 48” 4K oled screen using DLSS. Msaa x4 and capped at 60 fps( personal preference) is just right for me. My opinion still is DLSS was a good addition. Not everyone needs it or benefits from it so no harm using it or not.

Yup, love the p-47. I’m not very good with it, but it’s still my favorite.

Please consider lower ( cutting in half ) the trim gains in the clickabledata.lua. Dropped to .0125 the trim control on all surfaces is much, much better. You can actually trim the plane straight for reasonably long periods. 30 second fix

If you like the indicators on all the time you can go into the editor and find the layer called indicators, unlock it, click on it and in the properties above, uncheck “hidden”, then they will show up when the profile starts. Thats how I set mine up. If you want the switch to match, unlock the “indicator SW” and change the initial/start position from two to one in the properties. Then save the profile.. If you don’t want the splash screen, you can delete the layer ( first one) in the editor, or move it to the very bottom layer.

Dropping the gains to 1/2 feels great! That’s the way it should be!

Thanks! It took much longer than expected but Helios needed some pretty drastic changes for the variant switching to work ( also applies to any aircraft with multiple variants using json interfaces). One guy is working on a d-9 profile( hopefully still after it) I’m about halfway done with the f-5 now, after that I think I will either do a Spitfire, unless the f-4u releases before, then I will be all over that one

Your monitor 5 should be x = 2688, no? [5] = { x = 1920, y = 1600, width = 768, height = 1024 },

P-47D Profile Version 1.0.0 You MUST be running Helios Version 1.6.606 or higher for this profile to function correctly. This profile will automatically switch between the three variants, depending on which one you are flying. This profile is laid out as a "builders profile" (I call it). All of the components are there, but not necessarily grouped into panels based on location in the aircraft like most profiles. Also there are no panel backgrounds mimicking the cockpit. I wanted to make it functional for single screen, but easy to pick apart for users with multiple screens. Download Here--> https://github.com/HeliosProfiles/DCS-P-47D-Thunderbolt-Profile-by-MadKreator37/releases/latest or from User Files here--> https://www.digitalcombatsimulator.com/en/files/3335547/ For support go here--> https://discord.gg/T8vg5MSa ( CaptnZeen Discord) or Here--> https://discord.gg/yegshUzT (My Discord) Youtube: Start and controls overview ( kind of long and boring)--> https://youtu.be/09ZnmlZnd_Q?si=qqnFVx_6CGP_gFPK Current issues: 1. ADI Zero knob doesn't really work as it should (WIP) 2. the virtual throttle quad controls can be finicky. They are more for indication but can be used for boost mixture and prop rpm. 3. the rotation on the fuel primer can act up. and there is no input on that control. If you don't want the splash screen every time you start it, just delete it from the editor ( first item on the layer list), or move it down to the bottom-most layer so its behind the background.

P-47D Profile Version 1.0.0 You MUST be running Helios Version 1.6.606 or higher for this profile to function correctly. This profile will automatically switch between the three variants, depending on which one you are flying. This profile is laid out as a "builders profile" (I call it). All of the components are there, but not necessarily grouped into panels based on location in the aircraft like most profiles. Also there are no panel backgrounds mimicking the cockpit. I wanted to make it functional for single screen, but easy to pick apart for users with multiple screens. Download Here--> https://github.com/HeliosProfiles/DCS-P-47D-Thunderbolt-Profile-by-MadKreator37/releases/latest or from User Files here--> https://www.digitalcombatsimulator.com/en/files/3335547/ For support go here--> https://discord.gg/T8vg5MSa ( CaptnZeen Discord) or Here--> https://discord.gg/yegshUzT (My Discord) Youtube: Start and controls overview ( kind of long and boring)--> https://youtu.be/09ZnmlZnd_Q?si=qqnFVx_6CGP_gFPK Current issues: 1. ADI Zero knob doesn't really work as it should (WIP) 2. the virtual throttle quad controls can be finicky. They are more for indication but can be used for boost mixture and prop rpm. 3. the rotation on the fuel primer can act up. and there is no input on that control. If you don't want the splash screen every time you start it, just delete it from the editor ( first item on the layer list), or move it down to the bottom-most layer so its behind the background.

Now that the new Helios release is out, over on GitHub is version 1.0.3 of the profile. This should fix all of the UFC woes. Update Helios, Update the F-15e plugin, then download and install ver 1.0.3 and it should be good. If you have a modified profile and don’t want to install a new profile version, message me and I will show you how to fix your existing one.

Now that the new Helios release is out, over on GitHub is version 1.0.3 of the profile. This should fix all of the UFC woes. Update Helios, Update the F-15e plugin, then download and install ver 1.0.3 and it should be good. If you have a modified profile and don’t want to install a new profile version, message me and I will show you how to fix your existing one.

You can hook the ipad up to the pc using an app like SpaceDesk. It will turn it into an extra monitor, then you could run Helios Virtual Cockpit as Trigati suggested. Then you would get displays and controls on the ipad.