sobe

I am using some mods for my F18 Helios setup and as a result, the green letters and numbers on my HUD are a little light and thin for me. Does anyone have a mod that just makes the letters and numbers on the HUD a dark green or black?

I am using some mods for my Helios setup and as a result, the green letters and numbers on my HUD are a little light and thin for me. Does anyone have a mod that makes the letters and numbers on the HUD a dark green or black?

Similiar issue. I set a deadzone of 90% for each rudder pedal so they would not be active until I pressed them all the way down.

OK. Perhaps this is a "stumper." When I flew BMS, I had a mod that made a beeping sound as long as you had the speed brakes extended. I have tried to figure out how to do that in voice attack with Viacom pro, but can only get one beep. I need many beeps until the speed brakes are retracted. Is there any way to do that? BTW, I imported the beeping sound from BMS, an ogg file, and changed it to an MP3 file.

Bailey I am compiling a list of either my user errors or issues with your F18 profile. This will take several days to do. For example turning the Tacan on and having the channel entered does not seem to put the coordinates in the HSI. I am not sure if this is my error or an issue with the profile. I will get back to you with this and other issues that I find. Do you want me to PM you with my list? I am sure that most issues are caused by my lack of understanding and not your profile.

I understand a joke, but IMO, the project manager for this April 1st joke should be reprimanded. Why? Because yesterday was not April 1st so I spent a number of hours trying to find a nonexistent virus that I thought infected my computer. Having no landing gear while trying to land on a carrier is not a joke IMO. OK, have it happen once and then a counter should have turned it off.

"You have to use the emergency gear Handel to activate the gear." Where is that?

Bailey So far your F18 profile seems to play nice with Viacom Pro. I noticed that you didn't have a custom command for Altitude Hold so I used your Attitude Hold example and copied it to my own profile and made the appropriate changes. So far no sound issues.

Perfect. thanks.

Does anyone have a PDF of the controls on the throttle quadrant?

Just got my new computer and now cannot select my build version. I am only using the latest Open Beta.

Fakum Yes. Just make sure you coordinate the name change with BOTH the monitor config file and the lua init file.

Fakum I may be one of the lucky ones as both of my monitors are the same 1920x1080 and some users have said that if your monitors are the same, the viewports will work fine. I have no idea if that is the case, but for me, they work with no mods.

Fakum I am not sure if this is what you mean, but here is an example in the IFEl init file from Capt Zeen: ------------------------ added by Capt Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_IFEI") ------------------------ end of added by Capt Zeen

I would think that this could be done, but you probably have to change some of the init files to a unique name for both the monitor config file and the inits for the specific module.

BluFinBima Just a suggestion, but if you include in the install instruction that:Hi Sobe, if you installed via the "Helios Setup.exe" program, the Visual C++ runtime should have been installed. It might help others.

I believe that when I installed Helios (not sure which one), the installer looked for the Visual file, but delivered an error. So I found the file myself and installed it and now everything works. I was not clear that installing with the exe file would have installed the visual file. I am not sure if it did.

The update today for Helios does not seem to work without Visual C++ "14.26.28127.04" Runtime Libraries (x64 and I cannot seem to find this program on github or on Microsoft. When I load a jet, the Helios profile disappears. OK. Found the Visual file and everything seems fine.

Use Capt Zeen's export file and copy and paste the lines from the Viacom export file. Do the same for future programs that use the export file. You can have only one export file. local lfs=require('lfs'); dofile(lfs.writedir()..'Scripts\\Helios\\HeliosExport.lua') -- VAICOM PRO server-side script -- Export.lua (append) -- version 2.5.3 -- do not edit next line: -- xxxxxxxxxxxxxxxxxxxxxxxx local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[scripts\VAICOMPRO\VAICOMPRO.export.lua]]) local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') dofile(lfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Tech\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

I believe the latest update eliminated the need for any mods to make the MFDs and RWR readable on a second screen. Correct?

I may be holding a class for a few people on how to install and use Helios. I just want to verify that Capt Zeen's profiles can be used on a regular monitor (a non-touch screen monitor) with just the use of a mouse. Please verify.

Habu_69 I tried the program you suggested, but could not get it to work. I cannot figure out what I am doing wrong. I am running Helios, but I don't think that is the problem.

slicker55 I just removed the existing Viacom and reinstalled it.

Since the latest update, it appears that my PTT buttons change depending on the airplane. In the A10, I use TX 1,2 and 3, but when I use the F18, TX1 and TX2 are used. In the past, TX1 and TX3 were used. I seem to recall a new command that changed the radios based on the plane, but I could not find it again in the manual. Is there any way to go back to the old way?

I cannot seem to find the new manual radio tuning commands either in my new profile or export folder. So how do you get them? got it