JG14_Smil

Lost that about the same time we lost manual gyro operation. Start looking through lua files... never know what you will find. There may be other bug fixes like the SAI we can do ourselves. I have not been able to fly long enough to test it, tietze. Any chance you had battle damage and lost fuel? Uh oh... foot in mouth edit. I put the R-800 ADF switch to 'on' and then contacted tower. The needle went from straight ahead, to (I think) the tower when the tower replied to me. It might work. One more edit... It did not appear to work when tested online. I remember that used to work.

OK, I am learning the concept and my APU temp gauge works! I need to fine tune the numbers and calibration to perfect it. I learned it is easy to reverse the servo by reversing the numbers. I've seen an oddity I hope I can overcome in the Brake pressure gauge. It will follow the gauge needle great going "up", but there is a delay before "my" needle will return to 0. For the record, none of the "Engine" or Hydraulics" suites have value ranges, only 'type of units' when doing a mouse-over.

I believe we lost that feature somewhere along the line... Welcome to the Club, Lib! The more you learn about BS, the more your heart will break when you compare it to the manual.

I have wheel brake pressure responding with "0" and "4", but needle goes half way. I chose these numbers as that is what the gauge face says. I think I'll be able to get it by experimenting with the numbers.

Thanks Gadroc, that was a big help. Looking good so far on the APU temp. The Engine Power Indicator has a value of 0-1 and it seems to work when I put that in. The other Linear gauges I have checked do not have number values for a range. For example, Gearbox Oil Temp has "Celsius degrees" as a Trigger Value, with no range numbers. Suggestions? Thanks for everything!

Not a lot of luck so far. I have two servos hooked up and I can manipulate them with Helios. I enter the Test Values and get the desired positions. My APU temp gauge will even move a degree or two when the simulation needle moves, but I can get no response from the other bindings I am trying out. I am careful to follow the instructions in your post above. Is there any way to troubleshoot and test the values being sent from DCS BS? I am guessing these should be "-6000 to 6000" (?)

Read the link, Mojo. Gadroc, do we need any special lua lines for the servo binding properties?

OK.. Helios is talking with my Servos. Just need to get it worked out.

I un installed then installed to the new folders and all is well with my profile (I did not use default install path). No luck with getting a servo to work yet. I've got that weird Phidgets bug that won't let the Phidgets UI apps run, even though Helios LED controllers work fine.

Is the crash Profile related or Helios startup?

SAI is usable now and it seems more accurate than the regular ADI, even with maneuvering. Just remember it reacts to speed changes (as it should). May need some more drift added.

Yep, dogfighting in outer space was so realistic :)

Any special installation instructions?

I second this. Include the Blackshark data in this too, please.

In the past it was always a good idea to empty the tracks/multiplayer folder every so often as it fills with trk files each time you go online. I do the same with logs and keep only a recent one if it is needed. Be sure to use LAN for speed in MP options. Just something to try...

Moved this file to the Mods section.

Helios needs an Aero desktop.

Helios has never caused a loss of FPS for me, ever. I do run a simple profile though, with only gauges and a couple indicators. It is the extra monitors themselves, not the Helios that affect FPS (from what I have seen). I always used to love high FPS when simming with one or two monitors. Now that I run a large setup, I optimize it all to run at a steady 30 FPS and I am very happy with it. You should not be having any trouble with your signature system, unless you are running with Mirrors enabled.

It works for me because I fly smoothly when I use it. It is a backup electrically driven gauge and it does what it is supposed to do. You need to uncage it early in the startup sequence that the average Ka-50 pilot does not do as they use Auto start. You uncage it when you need it if you are going fly like a Hot Dog. The modeled drift was insane though and this is better.

SoftTH lets you run full screen.

I cant imagine flying with a regular monitor anymore. :)

-- Constant drift ConstDriftYRate_Scale = 0.0003 -- rad/sec ConstDriftXRate_Scale = 0.0003 -- rad/sec above values seem to be working for me so far in making the SAI more realistic (IMHO). I've worked with gyro operated instruments before and the BS SAI drift seemed excessive to me. I really do need to test it more to see if it is correct. yadayada\Mods\aircrafts\Ka-50\Cockpit\Scripts\STBY_ADI\Device\STBY_ADI_Prop.lua

6400x1920... I don't zoom :)

"0" is bad if you should be using a PLP monitor setup. I use the following line to center my HMS on my 6400x1920 setup. "math.rad(14)"

Ka-52 Just saying... Only other A/C I would like to build a cockpit for and my wish for DCS.