JG14_Smil

Erforce, I'll go over the list this week. My latest nit is the loss of the EKRAN turn indicator ("Queue" lamp) that is supposed to light up as a reminder of an upcoming waypoint change. I remember that as working in the past, but it could be as far back as BS1. I'll start paying more attention to the other three EKRAN indicators to see if they are duds too.

I agree, will. I found the FPS graphics.cfg mod (and a couple more mods) to be helpful for smoother FPS. Of course, now I miss seeing all the items like roads and such, but smooth is pretty important to me. Look on the bright side, you are not losing simulation features on each update like veteran Ka-50 users are.

Hello, make sure your throttles are set to "Auto" to get full power. (I think it is PAGE UP key twice)

Hello, I noticed some oddities in the GNSS pages in the latest updates. I believe the manual has something about the files you can edit and add to a miz file. I'll see if I can find it and if we can learn from what you do.

Send a keystroke when on, then again when off and it works fine. It has been a long time since I have seen TM coding, but it should not be hard to do.

Pause/Break key does it for me.

The red RM2 arrow on the ABRIS works fine. It is slaved to the R-828 (as is the ARK-22), so you need to be tuned properly there. If it still does not work, you need to replace your beacons.lua file. Let me know if so.

DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\Devices_specs\HUD.lua file has the line to set HUD brightness at startup. "initial_brightness = 255.0"

I'm glad to hear it works. :) I believe it will still need one or two recages an hour for calibration.

As PoleCat says, PTT is the way to go. I note that even with my PTT, I'll get an odd rear view that shows up if I don't annunciate a certain command clearly. Like you, I've disabled any links to this rear view, but it will still happen at times.

This JGSME ready mod makes the Ka-50 backup Attitude Indicator usable. Use JGSME or manually over-write your backed up original file.

Hi Gunner, That 'half-cocked' refresh rate only causes terrible screen tearing for me. Be sure to try without it.

I noticed that the R-800 ADF function worked for me online with the STP server that is hosting the radio "classics" channel, but it pointed to an area with nothing there. The radio tower was a few KM away. I wonder if this was due to trigger placement or coordinates error.

There is nothing wrong with the switch you wired up. It is the controller that does the work. That is what you need to learn about. You need to tell more about how you are controlling them, then you can see where you will need the different types of switches. The magic happens in the controller, not the switch.

Keep your eyes open for EpicUSB and expansion module. There are probably people that own them and probably don't even know what to do with them any more and if you can get them at a decent price, you make the biggest score in pit-building.

How large and how much function do you want your cockpit to have? You need to start picking and choosing if you intend to get it down to 'only' 128 switch leads. (not being a smart-arse, Bad CrC and my cockpits both have well over 300 switches in use and Helios can eat them up like candy when you start using the bindings). I can wire up well over 600 leads (bring on that Ka-52!), but I have been collecting expensive hardware for years. I am glad I did it now.

Manual entry waypoints in the PVI-800 don't seem to auto switch. They never have since BS1. You have to change the numbers manually as you have found. 'Automatic' flight plans are made in the M.E. The BS manual does not match up with our BS, it never has, and with each DCS World upgrade it matches up even less. We read a lot of it for no reason at all.

Quick work-around would be to turn HUD brightness all the way off.

I think it has to do with the gyros. If you reset your trim after making a turn, it stops what you describe. I am talking about the actual 'reset trim' function, which I map to a button. I don't use it in flight. Leaving your DT/Dh switch in the middle position while taxiing may also help.

I see... good find. I know that displayed a red arrow not too long ago. I see the RM2 heading indicator in the low left corner of the ABRIS screen has a yellow box around it.

If it is seen as a device, try ADD INTERFACE and see if it shows up.

Hello Gunterlund21, Helios is covering your shkval up because it probably needs to be in the same spot as Gadroc's opening that allows it to show through. Don't worry too much about monitor ID numbers, just do reset monitors and go with it.

I get a solid 30 FPS with my 6400x1920 PLP setup. PLP has good and bad points and is not for everyone. My TIR needs to be every bit as sensitive if not more so than my single monitor setup for looking around. The larger the viewing area, the more speed the TIR needs.

Bezels in a multi monitor setup are terrible to look at. I never used to think so, but I do now after living with it. They are fine until you use TrackIR.

Gadroc, Thanks very much for the new Helios! I remember you mentioning something about 'opening it up' and I was wondering if it would be possible to make some fixes for the small list of lua exports that do not work correctly in Helios/BS. Certain bindings are mixed up, things like that. There is a list somewhere. Just wondering...