sobe

I am just getting into the F14 (after flying the F18), and have some issues that I cannot seem to resolve. First, when I use a button on my joystick to get to the RIO (#2), I cannot seem to get back to the pilot using another joystick button for the number 1 key and have to actually press the 1 key on the keyboard. Is that normal? THIS APPEARS TO BE A KNOWN BUG "When rebinding Pilot/RIO Seat selection (1 and 2), cannot return to Pilot Seat. Second, I understand what the A key does, but when I am in the pilot seat and press the A key or press it twice (both on the keyboard and on my joystick), the jester wheel does not appear. What am I doing wrong? SOLVED. HOWEVER THE CENTER FIX FOR THE JESTER WHEEL IS STILL NEEDED AS OF TODAY. As I run Helios, I like the pilot view of the HUD to take up most of my game screen. Is there a view command similar to the regular RALT Numpad 5 to set the view the way I like it. Boy is this module going to take me a long long time to learn.

What is the best method to update the Jester module?

I just installed the Jester addition and was wondering how you update the Jester commands. When I installed Jester, I added the 4 commands to the main page as explained on page 37 of the manual. When I update the main program with substituting the DLL file, I assume that this does not update Jester. So I guess I have to download the new AIRO.dll and put it in the extensions folder. Do I also have to then again import the AIRIO.vap file and again copy the 4 commands into the main program?

Home Fries I am thinking about getting the F14 module. Because of the F18, I now have 4 TM cougar MFDs. Reviewing your profile for the F14, I notice that you have 2 MFDs for the pilot and 2 for the Rio. I assume in the normal course, when you change from one to the other, the MFD functions also changes. If so, would it be possible to have the pilot MFDs on MFD 1 and 2 and the Rio MFDs on MFD 3 and 4 on a permanent basis so that I can place your MFD overlays on each of my 4 MFDs? I hope I explained what I want to do correctly.

OK. I understand what you wrote about config files, but I do not understand how to do it your way. For now, I simply made 2 config files, one for each module and swap the files depending on the module that I am using.

I was just thinking the same thing as Caput 58. I was configuring my new Trackhat for 2 different modules and it says both configurations. I then went to SRS and realized that I had to override the keys for the F18 with the new keys for the A10. It would be nice to have separate ini files for each plane.

I am using the Trackhat clip plus on the right side of my head and my 2 monitors are stacked vertically, with the camera on top of the top monitor. I watched a video on how to calibrate the clip, but my "toggle calibration" remains greyed out no matter what I do. Is this function not working in the Trackhat version of the software?

I am using the Trackhat clip plus on the right side of my head and my 2 monitors are stacked vertically, with the camera on top of the top monitor. I watched a video on how to calibrate the clip, but my "toggle calibration" remains greyed out no matter what I do. Is this function not working in the Trackhat version of the software?

I just received my Trackhat clip plus and the head tracking camera. I tried the trackhat clip plus with my old Trackir camera and software and it worked. However, when I attached the Trackhat camera and software, I get the three green plus signs [plus one red plus sign], and the left camera light is blue and the right camera light is red (?) and the clip does not work in DCS. I tried both the flightgear and the freetrack 2.0 enhanced protocols. The mapping properties scales and the green crosses move, but the cockpit in the game does not. I have deleted my controls for trackir in the F18 game controls>axis setup and in the game detection tab, I inserted DCS.exe in the bin folder. However, no matter what I do, the software will not work in DCS. If someone has the Trackhat clip plus, software and camera working, please let me know what I am doing wrong. Update: If I start the trackhat software with the Freetrack 2.0 enhanced protocol and the default.ini, then at the top of the trackhat software box, it says: “trackhat 1.2p7 opentrack:: default.ini::Black Shark” and the software works in Black Shark but no other module. If I use the Flightgear protocol, no module works.

I was trying to help a fellow flyer with the A10-c and the Helios Loz profile as updated by CaptZeen. He has 2 monitors, 2560x1440 and 1920x1080. The 2560 monitor is the main monitor and the 1920 monitor is a touch screen monitor. For windows purposes, the 1920 monitor is to the right of the 2560 monitor. In the game, I had him set up the monitor resolution as 4480x1440 and the monitor configure file set the GUI and center specs as 2560 and 1440. The Helios 1920 screen was fine, but the 2560 screen cut the game screen by about 25%. That is, the part of the right side and bottom of the game screen was blank and the game only appeared in the remaining 75% of the screen. The same result occurred when we used 4480x1080. When we used only the 2560 screen, the game took up the entire screen. I am at a loss as to why this is happening. Any thoughts?

BaD CrC Yes and I have not checked the box in the game that seems to allow the trim function to control the trim for the rudder.

I am having some problems controlling the BS with my TM WH joystick and would like to know what others use for the pitch and bank axis settings for the dead zone, saturation and curves. thanks.

Got my refund. They were very nice about it. I only lost money because of the currency changes.

I am not sure if it is me or the profile, but sometimes the profile freezes and will not accept input. I generally restart the profile and it will generally then work. So is anyone else having freezing issues with this profile? All of the other profiles of CZ work perfectly so maybe something in the new code????

Not yet. In fact today, I requested a refund.

If you are finding that the panel buttons in the lower left are hard to see or reach and hit accurately, I have found that moving most of them to the left side of the profile mad them easier to see and hit.

Some videos on youtube by Virpil and Nobifier

"Num2 - RCtrl - RShift" Cockpit Camera Move Down That did it. Thanks

Here is a screenshot.

The top part of the HUD does not appear in my Hud screen. I know that in the A10-c, you can adjust the seat height so that you get the full HUD, but I cannot find anything like that in the Blackshark. For example, I cannot see the airspeed marker and the IAS scale even though I am going more than 50 kph.

What about an "A" on the left side? Are there any other letters that I should know about?

What does the "H" symbol in the flight controller position indicator stand for? I am referring to the graph that appears when you hit enter+RCTRL. Pages 13-11 and 12 do not explain the H.

I do not have the F14 module and do not expect to buy it. I have noticed that a huge number of posts in this thread relate to issues with the F14/Jester addition to Viacom Pro. My suggestion is that there be two separate threads, one for just plain Viacom and one for the F14. That will make hunting done past issues much simpler

I recall that there is a method to read the lessons in a text file by unzipping the missions and then doing something....but I don't recall what. Any help as I would like to get a startup checklist from the first mission.

There is a little trick to determining the coordinates for the 2 viewports. Load the profile in the profile editor and then on the left side, grab the panel>generic and cover the viewport that you need the coordinates for. On the right side, the 4 coordinates that you need should be listed-BUT YOU HAVE TO ADJUST THE COORDINATES FOR YOUR MONITOR SETUP. Use those for your monitor config file and presto, you are all set to go. I neglected to mention that this idea originally was suggested by Slippery_Rat on the SimHq forum. He has some great tutorials on Helios on that forum, but unfortunately, he seems to have ceased publishing his suggestions and tutorials.