sobe

I have a number of viewports showing on my second screen but for some reason the PLFD panel is not showing up. Below is part of my init file and monitor config file. Any thoughts? ------------------------ added dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_PLFD") ------------------------ end of added F16_PLFD = { x = 3166; y = 739; width = 229; height = 76; }

I have decided to go with the MFD darkening mod and use a snap view to see the EHSI until this issue is fixed (someday).

mcmike It appears that you have done a fantastic job of doing the first Helios profile for the F16. However, as a user of CaptZeen's ready made profiles, I am having trouble figuring out how to use your profile and how to incorporate the viewports that I have included in the monitor config file for the MFDs, RWR, DED, EHSI, CMS and the fault panel with your profile. Some instructions would help. I am running 2 1920x1080 screens.

A question: The info on the chat system states: Note: client can't interrupt sound data from peers to his PC from simulation. n order to use another speech software you have to return to Main Menu, open OPTIONS - SOUND and uncheck 'Voice Chat' checkbox. Does this mean that I cannot use Voice attack while AT THE SAME TIME using this chat function? I have this chat function set up for button 3 and Voice Attack set up for buttons 4,5 and 6. Is this a no go?

Goblin No. Target is supposed to work with the Virpil base and the TM WH grip by changing the VID/PID numbers, but it seems that it is not easy or a sure thing.

The person at HavocCompanyClan that does all of the great Virpil tutorial videos on YouTube would do a video on how to get Target Software to work with a Virpil base and a TM WH grip if Virpil would lend him a TM WH grip. Any chance of that happening? This would be a great aid to us nontechies that keep screwing up the attempt to run target with the TM WH grip and a Virpil base.

Same setup. You need to get it updated before you go to make the profile. I just spent 9 days with Virpil support to iron out my issues when I tried to use the TM WH VID/PID NUMBERS. We can talk on teamspeak if you want to.

Thank you CZ. I think I looked at the file for hours and never noticed the missing = sign.

Here is an example of a lua file that does NOT appear in the game drop down, but does appear in Windows file explorer. 2_monitors-FA18C.lua

I am having a really weird problem. I use notepad ++ to modify lua files with no problem. Now, all of a sudden, when I change a lua file such as the monitor config file for the F18, the revised lua file no longer appears in the list of monitor files available in the game drop down, although it continues to appear the the list of files in file explorer. Why?

Yes the default for the A10 is retained by the WarBRD base and TM grip. As for using the VID/PID with Thrustmaster’s numbers in the profile settings, I have spent the last 9 days with Virpil tech support as when I used the TM numbers, everything got screwed up. The bottom line is that target compatibility is hit or miss now and Virpil is working on something that might improve the use of target. For now, I am just going to change bases when I want to use target.

I do not use Target. Rather, I use the standard game setup and then use the paddle switch as a shifter so that I can double the commands on each button. This is more than enough and it works for the stick, throttle and panel.

I have had no issue using the WarBRD base and TM WH grip and the long/short presses with the A10-c.

Snacko I have had no issue loading the profile. Don't know what that means. However, I have another issue. I have used CZ's monitor config file for me without any changes as he has the same size monitors as I do. However, in today's update, the monitor config file has different numbers that do not load properly with the "b" version of the profile. So I went back to my prior monitor config file and all viewports loaded fine except for the RWR. The viewport numbers for the RWR based on my prior monitor config file should have worked, but now I get a blank RWR. I did change the lua file to the following: shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.6 shaderLineDefaultFuzziness = 0.3 shaderLineDrawAsWire = true --shaderLineDrawAsWire = false shaderLineUseSpecularPass = true but no joy. UPDATE For some reason I have the RWR viewport name in the monitor config file different from the name in the RWR lua file. When I conformed the names, the RWR appears but really impossible to read whether I use true or false for shaderLineDraw Update to Update: I got the RWR to work and am able to see it on the second screen although a blank on the main screen. shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.06 shaderLineDefaultFuzziness = 0.03 --shaderLineDrawAsWire = true shaderLineDrawAsWire = false shaderLineUseSpecularPass = true

I have set up my JDAMs to hit multiple mark points, but when I get to the first one, a IAM LAUNCH ABORT warning appears in my MFDs. Why? I have not changed the default setting in the DMS for the GBU 38. I could not find anything in the manual on this.

I finally figured it out. My old CH pedals seemed to have their toe brakes sticking even though I had the deadzone set at 95 and inverted them. So I blanked out the brakes from the axis list and set a button on my throttle for an on off brake control and now all is fine. Calibrating them in windows did not solve the problem and I do not use the CH manager. So this was the simplest solution.

I am 75 years old and retired and I could not have said it better than Hammerfly did.

I wanted to calibrate my Warbrd and Warthog grip using 044F AND 0402 for the VID and PID. No matter what I do, it keeps saving to the default valves and not the valves for the Warthog so Target will not run. It saves the numbers as 03EB and 2046. I am running 190930 Virpil software. I know it was able to do it before so I cannot understand what I am doing different. Any thoughts?

I am having an issue with the A10c and my throttle. I have installed this mod and calibrated the throttle. Everything seems to be working fine except that I am having issues with taking off in the A10c. I set the flaps for 7 degrees and many times I hit the fence at the end of the runway. I have checked my rotation speed and lift off speed with the weight of the A10. When I set the flaps for full, I take off ok. In the game, I have set the throttle as a slider and everything else as defaults. I don't recall having this issue before inserting this mod. I have calibrated the throttle twice with the included calibration tool. The in game gauges go to just below 100 on the RPM for both engines. I am just trying to figure out what is happening and wonder if any one else is having similar issues after installing the mod.

Is there any chance that the PTR switch is reversed by accident (able and stow seem to be reversed????) or am I just crazy?

I may be wrong, but I think I figured out how to do it. First I go to the divert page and click for Kobuleti which is way point 63. Next, I switch the dial from flight plan to mission and Kobuleti shows up in the TAD as the steer point number 63. While the Tacan station is not the sp, Kobuleti is so it seems this is close enough. Any thoughts?

I just wanted to check, but when you navigation with the Tacan button depressed, does the Tacan location become the steerpoint on the TAD?

HunchyTheHuncher Very nice. If I can find someone locally (Bend, Oregon USA) to print the enclosure for me, is your list of the various items needed to assemble the project complete or do I need additional items? I am a beginner on things like this.

Maybe 2 is actually slower than 8. Oops.

I only have a Amazon Fire tablet so I need the app put on the Amazon app store. Thanks.