mhe

I am having a great time with my SteelSeries Arctis Pro Wireless. Not the cheapest option but very happy with it. For wired I did use a BeyerDynamic MMX 300 before that, also pretty nice.

Thanks, Chuck, awesome as always!

Having a TrackIR 5, a Tobii 4C and an Oculus Rift, I can tell you that for flightsims, the Tobii doesn't hold a candle to the other two. For the money I'd rather go TIR5 + UTC Mk2 clips (sold by a user on this forum).

So after yesterday's patch I can confirm it makes no longer a difference whether you run the full Export.lua or the stripped down version I made before. Performance suffers again. :/

As far as I know yes, but I have never tried it in practice.

Good question, I'll look into that. We are talking Hornet/Hog here, do we? Because the stripped version only supports those two, the rest have been removed for testing/performance purposes. I'll get back to you once I have managed to modularize the script a bit more.

Gsync HDR stuff still is not really ready, wait a bit until they sort their stuff out.

Then it is down to server rules - if the server forces a disable of Export.lua then there is little you can do about it other than talking to the admins. There has been cheating with Exports so this is the reason why this option is there. I have successfully tested this in Multiplayer as well but you have to allow export sensors and export objects in the server rules (advanced settings when you create your own servers, it is not allowed by default). If the server does not allow these, Helios cannot work as the Export.lua doesn't even get called by the DCS client. It is a limitation we will have to live with unfortunately unless ED decides to support our touchscreen interfaces officially - which would be awesome.

Yep, 3840x3240 here and it's doing the same thing. Did it from day 1 so it took me a while to realize it shouldn't be that way.

Knob just adjusts the brightness of the HSI waypoint sequence but no other elements of the screen. Also, if waypoint sequence brightness is tuned down, it affects the HSI screen if it is being displayed on one of the upper DDI's instead of just the AMPCD screen.

Tried at 650 knots over the Stennis and thankfully the ship deck was behind me by the time the nose came down a bit.

It is possible in terms of Helios, however we cannot export displays over the network, so you wouldn't see any DDIs, AMPCDs, RWR info etc.

I was wondering the same thing recently and found out that the script works perfectly but the multiplayer server I was on simply forbid ANY kind of export (not even TacView would work), so that might have been the issue in your case as well? Just to be sure, please try again with a local instant action session so we can make sure I'm not hunting ghosts here.

Well basic stuff almost works already but since I don't do FC3 please don't get your hope up for the planes you want. However it should be easy enough to extend my version since it is mainly a slightly modularized version of Zeen's code.

That is my plan. Make a default export Lua that only queries the used aircraft and probably the map and trigger only what is needed and pass these parameters as arguments to the called scripts so they don't have to query that separately.

Since I get quite a bit of FPS loss with the default CaptZeen Export.lua with all the bells and whistles, I created and tested a stripped down version that just supports the F18C and the A10C. Performance is significantly improved in my tests (slightly more FPS but a BIG reduction in frametime fluctuations). Next step will be splitting apart the whole script into separate files to make sure only what you actually need does even get parsed by the engine. See attached file and make sure you uncomment the lines in the end for SRS, TacView, Ikarus etc in case you are running these tools. I'll post results as I am making progress. Please let me know if this increases performance for you guys. Export.lua

Only works with the hook bypass switch in carrier.

Fusion 360 and OnShape. Sketchup is not bad, but once you tried the other two, you'll begin to realize what you missed out on.

As a big fan of Helios, I am naturally interested in optimizing the LUA stuff that makes it all work, so I have a few questions as to how DCS handles this script. 1.) How often and when does it get run? Every frame? 2.) Is there a way to write and read from memory or is there any persistence between runs? 3.) Can I benchmark the performance of my scripts somehow? I know if I press RCtrl+Pause twice, I get extended performance info and the second last line contains a LUA CPU load: what exactly is that? One core/thread? 4.) Would it be possible to offload the LUA stuff to a separate CPU core? If so, how? I am a LUA noob but used to be quite good in Perl and PHP, so I hope I'll be able at some point to squeeze a bit more performance out of this. Live and learn as they say...

So we actually can adjust at which throttle level the AB kicks in? Without using curves?

I'd go with a higher resolution and capacitive. I have tried quite a few screens and what I ended up sticking with is the Hanns-G HT225, amazing piece of kit, checks all the boxes and is not too expensive.

Approx 45-47 without Helios (just SRS and TacView in Export.lua) down to about 37-40. The drop is a bit steeper than on the Hog for some reason but I guess that will be ironed out eventually. I just wish SLI would work properly...

Got it up and running and it is a thing of beauty, thanks CaptZeen! If anybody needs a screenconfig, I run these coordinates for a 4k main screen with a 1080p touch below it, vertically arranged and aligned on the left edge for coordinates. These values work for me, main screen is 3840x2160, touchscreen is 1920x1080 and DCS overall resolution is 3840x3240. Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 1.777778; } } -- Viewport to place GUI and menu on GUI = { x = 0; y = 0; width = 3840; height = 2160; } -- Bind GUI and tactical map to main screen only UIMainView = GUI -- Kneeboard config to show up on the main screen in the bottom right corner KNEEBOARD = { x = 3312; y = 1370; width = 526; height = 789; } -- Export for F/A-18C --LEFT DDI F18_LEFT = { x = 283; y = 2355; width = 380; height = 380; } --RIGHT DDI F18_RIGHT = { x = 1261; y = 2355; width = 380; height = 380; } -- RWR F18_RWR = { x = 1496; y = 2882; width = 174; height = 174; } --AMPCD F18_AMPCD = { x = 772; y = 2850; width = 376; height = 354; } --IFEI F18_IFEI = { x = 153; y = 2914; width = 524; height = 203; } --UFC F18_UFC = { x = 741; y = 2190; width = 455; height = 263; } -- END F/A-18C

Jabbers seems to like the new stuff:

Good to know, another reason why I feel I have made the right choice when getting a VPC T-50 base. No adapter needed, highly recommended. Thanks for showing these pics, I didn't know what the adapter looks like, I have to say I didn't expect it to be this cumbersome.