MadKreator

Stuttering for me is very random. A free flight in the p-47 on caucuses, microstutters like crazy, more so looking left and right when turning. But a Retribution mission on Sinai in the f-16 ( last night), aside from taxiing at the airbase with lots of objects and jets around, silky smooth the entire flight. ( 2d in SP with trackIR). I’ve never found a combination of actual settings that gets rid of it. This leads me to believe that it stems internally with how dcs processes all of the data in and out. My cpu and gpu aren’t even trying that hard on max settings yet still lots of random micro stutters and what seems like a skipped frame or two here and there. I can only think that the way DCS computes things is inefficient. But I'm no software engineer so what do I know

Fps is at 120, guess I should have mentioned 2d and not vr, and just in a free flight/takeoff mission doesn’t matter if it’s in the air or on the ground, opening and closing… All other aircraft are smooth as can be for me, just not the p-47

@SparrowHawk003I should add that helios1.6.603 did have a fix for the WSO caution panel, the indicator bindings were off by one. In version 1.0.2 of the f-15 profile it is fixed. If you had v1.01 and updated to helios 1.6.603 then there still shouldn’t have been any real errors, but the WSO caution panel might act funny. Version1.0.2 of the profile should work in either helios version. Another user updated to the new helios version and kept 1.01 of the profile because he had lots of mods to it he didn’t want to re-do so he just dug through the editor and deleted the WSO caution panel and dragged the new on from the toolbox into the profile. Its the same fix either way. When I built the profile I used every item Bluefin made in the helios toolbox to make it more efficient. There shouldn’t be anything different with the plugin…. It may have bugged out on you… you might just go to add/remove programs and delete the f-15e plugin.. the to documents/helios/profiles and delete the f15 profile and backups.. then 1:update helios to the newest version 2:re-install the f-15e plugin 3: install / reinstall the profile v1.0.2, in that order. If there is something wrong with helios itself, then CZ’s discord will be the best place to communicate. Over there we can get the helios developer involved if need be

What kinds of things? Want to hop over to CZ’s Discord and hit me up? Its a little easier to chat and share screenshots and things if need be. https://discord.gg/5Ant8cKX.

Probably true. Mine seems so start getting a visual around something like 6nm out or so. It’s so tiny on my screen I can’t tell whether its an actual “spotting dot” or if its the point where the aircraft are starting to render in. But beyond that range there is nothing visible, to my eyes anyway. I’m used to that, so no complaints here. Thats how dcs has been from day one for me.

I’m in 2d but same. I nvidia setting under desktop appearance adjusting digital vibrance will dull it out bit thats changing the global pc color palette. Of course it will vary monitor to monitor.

As title says. From inside the cockpit, when closing or opening the canopy its very jumpy/ stuttery, whatever you want to call it. From the external view its nice and smooth. Not a game breaker but i assume it should be a nice smooth animation like other aircraft. Easy test- Sit in cockpit- Close the canopy and watch it. I searched and didn’t see a report about it. I’ll delete if it’s a duplicate. …. Or am I the only one with this happening?

Adjustments would be great. I like technicolor 3 VERY vibrant, but just a touch too much. Dialing it back just a bit would be great.

*** Just an FYI for anyone that runs into it. For the Terrain Following Radar Controls- TFR Couple Switch, Flyup Switch and Switch Cover. The output bindings from Helios to DCS do not function at this time as RazBam changed the Device ID numbers during its implementation. These will be fixed in the next Helios Release with an updated interface.***

*** Just an FYI for anyone that runs into it. For the Terrain Following Radar Controls- TFR Couple Switch, Flyup Switch and Switch Cover. The output bindings from Helios to DCS do not function at this time as RazBam changed the Device ID numbers during its implementation. These will be fixed in the next Helios Release with an updated interface.***

Same here.. mic test sounds fine but the voice/radio test is very bad. I tried a few tests and just thought “ this sounds terrible, no way I’m using this”

No problem, I know its not really what you were looking for, just noting that the possibility is there to have the input data pulled for it, if your’e building a physical arc 210. I will dig through the lua files for it in helios and see if I can find anything related to the arc 210 data. I’m not 100% sure how it was accomplished.

I don’t think theres a direct way for that display besides using a viewport. In Helios, Bluefin created a text display version although it has the surrounding graphics. But I also believe thats a very involved complex task.He probably hand created the text characters as usual, then uses some lua calls to have the data pulled when necessary for it to display.Although I’d bet the core of Helios has a lot to do with making that actually work.

I was going to ask if it was only on the export screens. I had it happening when I first started exporting things and it was because vsync was set on fast. But I know you've been at it long enough, and haven’t mentioned any issues like this before. …. Ummmm I’m at a loss. Even though its a new update, might delete the fxo and metashaders folder I saved games and run a repair, just to cover the basics…. Did you unplug it and plug it back in?.. sorry couldn’t help myself, my work week has been full of that

I’m on a 5120x1440p monitor and I’ve never seen a spotting dot in the years I’ve been playing. Even now with “improved” spotting dot, theres no dots lol I can see the planes starting to render when they get close, but no dots on every enemy like what I see in VR. Do people on 4K monitors see these mystery dots? 1440p 16:9? I wonder if its just the odd aspect ratio? Right now nothing has changed for me To be more thorough: 2D @ 5120x1440, all graphics setting on max, motion blur and DOF off, heat blur low. Sharpening at 1, LOD at 2,( msaax2, x4, DLSS, TAA had no effect). Labels set to dot neutral. This morning I thought maybe I saw a spotting dot but it looked like literally 1 pixel. It could have been the plane starting to render in too, it wasn’t all that far away. I only noticed it because I knew a plane was there. Next to imperceivable if I wasn’t really, really looking hard for it. Nothing even remotely close to the dots I’ve seen in VR ( Quest 2 &3)

Nothing on my end, they seem just fine on the helios screen. Haven’t noticed anything out of the ordinary.

yup I had the same. Very confused, then noticed I flipped the TFR switch up too far during startup

Found a little bug where, at least on my system, having SSS enabled while using DLSS cause massive shadow artifacts while rolling. Happens in all aircraft on every map I tried at lower altitudes. Much worse over cities. This was in f-16/instant action/freeflight/syria. -Occurs when using SSS and DLSS -Does NOT occur using SSS with DLSS off -Does NOT Occur using DLSS with SSS off Screenshots attached with settings.. I will attach a track, but oddly enough the issue doesn't show when I watch the track..not sure it will help No Mods, Nvidia settings at default. *Notice the dark random shadows around the scenery in the first two pictures.. and not there in the second two. f-16 syria dlss with sss issue .trk

No just imagining. I try to assume theres no over crowding, rude pushy people and jam-packed city-scapes. I picture my vacations to Hawaii, just in a different ocean 100% fairy tale

I would trade the high desert mountains of Idaho and 1gig internet for 50mb on an island in Greece any day! Download overnight, wake up to a perfect sunrise and a triple shot coffee, then sit down for a good… no, great day of (pretend) flying

I 100% agree thats where my misconceptions came from

I guess 25 years of flying radio control planes has my thoughts a bit skewed lol.. Of course RC planes don’t use trim tabs, just the whole surface to trim the model. I always thought the trim tabs we just small versions of the control surface to achieve smaller inputs, but they would move the same direction causing a small force to act on the entire aircraft. Never thought about a trim tab only acting on the actual control surface its attached to. You were clear, my mind wasn’t receiving it correctly

That video cleared it up! I understand how it works now

AHHHHH ! I see that tab is forcing the elevator into a different position. Not acting like a little elevator in itself.

Yes thats what thought,, trim tab up=elevator down= nose up… but when using trim up, visually the tab moves down, not up