sobe

Changing shaderLineDrawAsWireto TRUE helps a little bit but now it is not readable and not consistent with the RWR in the cockpit. Also, the HMD no longer seems to work.

Here is a picture of the blobs:

No joy. But I also think that I made so many changes to other files in order to get the 3 MFDs readable that there may be some interdependent issues between the RWR lua file and the other changes that I made so long ago that I cannot recall them.

The Virpil WarBRD base and the WH grip work with target if you change the USB id when installing the WarBRD base software.

Nic suggested that the reference to the RWR for the viewport be changed to FA_18C_RWR and that solved the location problem but did not solved the green spots.

YES. All I see is green light in the RWR on my second screen. Cpt Z---HELP.

YEP.

Sierra99 100% correct. I am thinking about switching springs to the heavier one, but have not yet done it.

I have noticed that in TOO mode, when I change the elevation in the HSI way point data page to match the correct elevation, the elevation in the JDAM display page/MSN, does not always change to the correct height. Is this me or a bug?

In the special section for BS, there are a number of boxes to chose. I am confused as to what they do. I have a WH Hotas with rudder pedals- Rudder Trim: It would seem like I should check this box? Trimmer Mode: there are 3 choices- Default-what does that do? Central position trimmer mode? Joystick without springs and FFB-since the WH has springs, I assume this is not applicable to me.

The answer from Nic: make sure the line dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") is in the lua file and before the line try_find_assigned_viewport("A_10C_RWR_SCREEN") or however the viewport is called for you talking about the _init.lua files here

FZG_Immel what I did was save my WH joystick profile in saved games, then loaded the game with the virpil joystick and then loaded the WH joystick profile into the virpil profile and redid the lever modifier.

I am not aware of any guide or video, but I have done it using: VID and PID and upload it to your device. VID 044F, PID 0402 That may not make any sense to you so if you want to, send me a pm and we can talk on my flight group teamspeak. It works 90% of the time, which means it does not work 10% of the time. I live on the west coast of the USA.

I am using the latest version of Helios and the latest version of Loz/Cpt Z’s profile for the A10-c. I have been away from the A10 for awhile and upon coming back to it, the RWR and CMSC viewports do not appear in the profile. All the rest of the viewports work fine. The viewport for the RWR is: ED_A10C_RWR = { x = 2520; y = 161; width = 175; height = 175; } and the init file contains the following lines: --added for Instrument Export Mod purposes = {render_purpose.GENERAL} update_screenspace_diplacement(1,0,0) try_find_assigned_viewport("ED_A10C_RWR","RWR_SCREEN") --end Instrument Export Mod adds The viewport for the CMSC is ED_A10C_CMSC = { x = 2776; y = 141; width = 230; height = 49; } and the init file contains the following lines: --added for Instrument Export Mod --update_screenspace_diplacement(1,0,0) --here just in case needed try_find_assigned_viewport("ED_A10C_CMSC","CMSC_SCREEN") I cannot figure out the problem. Any suggestions?

ZQuickSilverZ I have investigated some Trackir alternatives also (although not as thoroughly as you have done) The system that I am considering requires a lot less pain and effort to get it to work. Here are the responses from the owner of Trackhat to my questions: QUESTIONS: I have the Trackir 4 pro clip and camera. Both are on their last legs. So my questions are: 1. I fly the planes in Digital Combat Simulator. I assume your equipment is compatible with DCS. Correct? 2. As I understand your website, your wireless clip is compatible with my Trackir camera. Correct? 3. Will the Trackir software work with YOUR clip and MY Trackir camera or do I have to use opentrack? 4. When my Trackir camera goes and I switch to your camera, will I then have to use opentrack? RESPONSES: 1. Yes, our software works very well in DCS world. 2. Yes, the Clip Plus is compatible with the TrackIR sensor. 3. You will need to continue using TrackIR software with their camera. 4. Once you have one of our cameras, you can switch to our software.

-ICE I am glad to see that you are still involved in flight sims. I never could figure out what happened to you and BMS. I had used your BMS profile for many years. Is there any chance of seeing a 4.34 BMS profile from you? As to your issues, I have only 3 comments. Some at BMS indicate that the latest version of Helios is not BMS friendly so I have retained the original Helios to use with BMS when someone produces a 4.34 profile. Second, I run 3 monitors and found that Helios had trouble when monitor 3 used an HDMI plug as that seemed to confuse/control the helios monitor reset feature. My solution was to only use 2 monitors and unplug the 3rd monitor when using the Helios monitor reset feature. I then plugged back the 3rd monitor and use it for Teamspeak, etc with no issues. Lastly, perhaps I am misunderstanding your issues, but why not just tell Helios that everything is to the right of your main monitor(s) and then physically set them up the way you want to. Helios is not looking over your shoulder to see if you are cheating on your physical setup. Good to see you back.

I have fiddled around with my TM WH base and grip and my new Virpil Warbrd base. When I installed the new WarBrd base with my old TM WH grip, the WH joystick name was changed to " Right VPC WarBrd. " I am back to using my TM WH base and TM WH grip and no longer using the WarBrd base for awhile. However, now the windows game controller and DCS report that the name of my joystick is still Right VPC WarBrd. How do I get my WH TM joystick back to its original name of Joystick-Hotas Warthog? I uninstalled the joystick and reinstalled it, but the name remains Right VPC WarBrd.

I have had some issues with trying to use Target with the Warbrd base and WH grip using the id numbers for the WH hotas. It appears that when I use target, I get both a TM combined Hotas and separate throttle and stick controllers (for a total of 3 controllers) so the button numbers are all confused and target scripts do not work. Has anyone else had this issue?

I am using the Virpil base with the WH grip and using the correct Id for the WH grip and base so that is not an issue as it shows up as WH joystick. 0x044F 0x0402 If you change the VID/PID to that of a Cougar your PC will even recognize the stick as such, allowing you to continue using your TARGET functionality. VID=044F, PID=0400 Source of VID/PID info https://www.the-sz.com/products/usbid/index.php?v=044f&p=&n=

I sent this to TM support: As TM support requested, I uninstalled and reinstalled Target and the same thing happened. As soon as I clicked the menu button in the script editor, target would close. Today, I decided to click a target profile and have it open with target and it did. the profile compiled, but when I hit the run button I got the following errors: "Error (internal) cannot associate a filter with the selected USB HID device "VID_044F&0404" and "Error (internal) cannot associate a filter with the selected USB HID device "VID_044F&0402" "USB HID device with hardware id "VID_044F_0403" cannot be found." I HAVE NO VID_044F_0403 LISTED AMONG MY 6 CONTROLLERS (4 MFDS, WH THROTTLE AND JOYSTICK). 0404 IS THE THROTTLE "USB\VID_044F&PID_0404&REV_0100" AND O402 IS THE JOYSTICK " USB\VID_044F&PID_0402&REV_0100" ANY SUGGESTIONS?

I am using the new WarBRD base and the TM WH grip. In order to be able to use Target, I have changed the UBS/VID numbers to 044F 0402 but I am having issues with Target. So I just want to verify that I am using the correct USB/Vid numbers.

recondo I have the WH grip and WarBRD base and have no issues with DCS. I don't understand what you are saving in the pictures? Each individual controller? BTW, I changed the id of the base so the base and grip now are reported as a WH controller and target can be used or someone else's WH profile can be used. If you want to discuss this further let me know.

Is there a printable version of the PG map with labels for airfields, tacan, etc ?

Just got their email today.

From Bluefin If you hit the same problem that I reproduced, it is caused by Control Center trying to tell you that you need to enable the Aero Desktop. If you turn on the Aero Desktop, then I suspect that the problem will disappear. If this works for you, then I'll wait for the next release of Helios before delivering the fix.