Scofflaw

When you say wobble, what do you mean? The reason I ask, is that almost no matter how I trim, I cannot establish a fixed heading. It almost always starts to bank to one side or the other. I use the attitude hold to work around this, but I was wondering if it was just a lack of practice on my end. In regard to the difficulty, I own all the helicopter modules, and this is the only one that hasn't clicked with me yet. When I crash any other helicopter, I usually know what I did wrong, but not with this one yet. I definitely need more practice, and enjoy the process, so I'm not complaining. It took me a long time to figure out the black shark, and the mi8 took even longer. They both feel easy to fly now, so I'm hoping the Apache will too one day.

Unfortunately, I was unable to get this script working without the stutters. I often see other people complaining of stutters with export LUAs, but none of the fixes they propose work for me either.

Sorry, I'm not super familiar with github, but I downloaded the .zip from github (this URL : https://github.com/asherao/DCS-ExportScripts/archive/refs/heads/master.zip). Is this not the latest? On github, I see the tools.lua link on line 38 of this file : https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportScript.lua This matches the exportscript.lua in on my computer, am I using the wrong version?

The file date is showing 5/22/2022. Is there a newer one?

That will disable the script:

I found that line in ExportScript.lua. I was disabling individual parts of the export script to see if I could isolate what causes the stuttering.

Thanks! I had a quick look on DCS files to see if anyone modded it, but I never thought of doing it myself.

In my experience, he's just a little abrupt. If you get the aircraft pretty close to a hover first, then George will have an easier time. If you're heavy and doing 120kt, telling him to get into a hover might produce undesirable results. If you check the AC page, you can get an idea how hard he's pushing the aircraft - if I see he's redlining it and we're descending, I'll know I need to take over and recover. If you're telling him to increase altitude and he's descending, it's a good indication that you're heading towards a crash. I don't think George can recover from these scenarios.

I don't think it does anything - when I tune to 127.50 I still get the mission messages

I've had some success by setting George to weapons free with the gun. He can pick out targets quickly on the road and engage them. Once that's done, switch him off weapons free mode because he'll use up all your rounds trying to shoot the house further up. You'll want to progress up the road slowly: if you go too fast you'll sometimes end up right above your target and by that point it's too late.

Would it be possible to have an option to hide the lens arm of the HMD, similar to how the Apache hides the IHADSS monocle? I find the animation and blurry arm a little bit distracting.

Thanks, I'm glad I'm not the only one. I was a little bit frustrated; I used this mission to figure out how to use the radios as well, and after finally mapping all my communication buttons and figuring out the frequency, my wingman refuses to do anything useful. My wingman's only purpose is as an obstacle to avoid on takeoff.

I've been playing this mission frequently, because it's good practice for moving targets and it's fairly windy, so good flying practice as well. The issue I'm having with this mission is that my wingman is 100% useless. I've tried telling him to attack my enemy, attack my target, engage mission and RTB, engage mission and rejoin, etc. I've basically tried everything, and he'll just start flying in circles in the town north of waypoint 7, while stating "running in" and doing nothing. Almost every time he'll just crash into a building or terrain while engaging nothing. I've also tried waiting for the enemy vehicles to start firing at me so I can order him to attack, and he still just runs off. Any suggestions? One other question - I noticed I have to tune to 127.5 in order to talk to my wingman. That's not mentioned anywhere in the briefing or kneeboard; I had to go into the mission editor to find that info. Is 127.5 the default freq when not otherwise specified?

I just did a whole night mission through the mountains. I found it really disorienting and unnerving, but quite enjoyable.

Pretty sure ED said it'll never get APKWS.

I'm also using an xbox controller for the CPG position, and the TADS was drifting a lot. I had to put a pretty substantial deadzone (10) on both X and Y axes for it to stop.

I had a situation where I was only able to lase once for a second or two, then the laser just refused to fire ever again. I restarted the mission and on the second try the laser worked properly. I don't want to say it's a bug because I had maybe 25 minutes of CPG experience at that point, but for some reason everything worked on the second try.

Speaking specifically for the hind, on my PC, enabling mirrors will automatically drop the FPS down by at least 10 With a mobile 3060 and your resolution, I would definitely turn off MSAA. I doubt that would double your FPS though.

When things like this are added, do they typically update the manual? I'm really not complaining here; I'm usually excited to see new features and toys - I just feel like unless Wags makes a video, we have to figure some of these things out for ourselves. I really appreciate the DCS community going out and testing these things. You guys are much more patient than I am.

Thanks for taking the time to test this. My problem is not so much the FPS drop, it's the stutter. I don't mind if DCS drops from 120fps to 90fps, but even if it's running at full 120fps, the stutter makes it look choppy. I wish I had a more technical way to capture this information. I set the detail level to the lowest possible settings, and it still stutters with the script. I only have 1 script running, and it stutters. If I remove it, it's buttery smooth. I have no other mods or anything else running. I'm pretty certain the export script I'm using is just exporting too much data too quickly.

I tried the full OS reinstall, and even tried a new install on a pretty fast NVME SSD. In my case, I think the script I'm dealing with outputs way too much data at a very quick rate. I don't want to hijack this thread with my troubleshooting; I was just curious if maybe I overlooked something. Thanks!

Winwing.cn works, but their store page (https://wwsimstore.com) is down for me too.

I got it from : https://github.com/asherao/DCS-ExportScripts Right now for testing purposes, I don't have my HOTAS or TrackIR plugged in.

As far as I know, DCS doesn't support HDR; I believe the option was removed a while ago. If this TV has better contrast than your previous one, then you might notice some improved image quality. Generally speaking, 4k is always going to look sharper than 1080p, including all your other games and regular usage. I use a 49" 4k panel, and I don't find it harder to spot targets, but that's compared to my previous screen, which was 1440p. 4k is also 4x more pixels to drive than 1080p, so your system might struggle a tiny bit at higher quality settings.

I downloaded ExportScripts from github yesterday. The only script I have installed in DCS is this DCS-ExportScript. I tried a full windows reset, nvidia drivers remove and reinstall, reinstall exportscripts, the problem is still there I have streamdeck running, but it's a default install without any profiles. I tried removing it and I still have the problem. Nothing else running I did perform some more testing, with an FPS counter + graph this time. In the attached image, I ran the exact same scenario twice (quick start -> F16 -> Caucasus -> ready on ramp). On the top half, at exactly the same moment, you can see the FPS is very jittery, and I highlighted the stutters in blue. On the bottom graph, I have the script disabled (removed from folder), and it's perfectly smooth. I did narrow it even further down to \DCS-ExportScript\lib\Tools.lua. When this lua is commented out from ExportScript.lua, it runs smoothly. I guess this makes sense since this lua is the meat and potatoes of this script. --dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\lib\Tools.lua]]) -- remove for testing purposes I tried to have a look at Tools.lua to see if I could perhaps remove some sections to see if performance improves, but this starts to be a bit above my skill level. I did notice another DCS plug-in (DCS UFC Android App) has some users complaining about the same issue with the ExportInterval value causing stutters, but I don't think they were able to resolve that issue either.