mcmike

F16 Helios Profile Here is the profile- also note- lighting panel buttons are inoperative since they are not yet implemented on the f16 F-16Profile.rar

I would be happy to. There are a few things to note though.. 1)Helios profiles are setup according to the layout of your monitors, so you will need the rearrange the profile to match your monitor setup. 2)I have had to add a lot of custom key binds for functions that don't already have a default binding in the game (ex- lalt-B for INS CCW knob, etc). In order to use this profile, you will need add in those same keybindings into your game in order for the buttons to work. 3)Some of panels in this profile are hidden (like the UFC panel). You will need to touch (or click) on the UFC button to bring up the UFC. This allows you to have access to all of the preflight button needed for start up without having to cram the UFC on top of it. Once startup is complete, then you bring up the UFC. Not sure if all of this will make sense without having the profile in front of you. I am not at my Sim computer at the moment, so I will upload the profile a little later today when I can.

Here is the issue:on the ground at just about any speed above 40-50 knots, the F-16 drifts wildly- much more so than an other aircraft. This is true both during takeoff and landing. Here is what I have done so far to troubleshoot: -I have been reading the forums about optimal tweaking values for rudder Axis values (curvature, deadzone, etc.) but none of this seems to make a difference for me. -I have tested using an empty payload to eliminate balancing issues -Looking at the external model, the wheels seem to be stationary- not drifting - I view the controller mapping on screen and confirm that there is no unintentional input coming from the Warthog controller. Despite all of this, the Viper veers every time. At this point it feels more like a bug than an issue with my setup so I am posting it here. Any thoughts or other stories confirming this issue would be appreciated. Thanks

Cop- thank you. I did some quick tests and the press and release method seems to work for few buttons I tried. Much appreciated!

I have been using Helios and a touch screen for several years, but with the F-16 I am having a problem I have not encountered before. Helios appears to be working as it always does. When I press on a button on my touch screen, it is sending the correct key press through to the sim- I confirm this by opening up the options keybinding menu and then pressing the button in helios and confirm the screen jumps to the correct key bind in the menu. However for certain buttons in the F-16 cockpit, the button press animation seems to be extremely quick (e.g. a button on the UFC will only partially depress and pop back out, or for certain toggles, the switch will only go part way up or down but will not stay in the desired position. Also, if manually do the key press on the keyboard for those same keybinds, the buttons and switches act as expected. So this troubleshooting leads me to believe there is some sort of disconnect with Helios and the F-16 module (since this doesnt happen on any other module). Also, this does happen for every button- Most of the UFC does not work along with engine start- but sensor switches work fine. I am hoping a Helios guru might be able to help out!. Any thoughts would be appreciated. Thanks

Does Anyone know if it is possible to export landing light indicators to either an external app like Helios, or a device like a Saitek Flight Panel? I've seen home cockpits where status indicator lights are lit up so I assume its got to be possible but can't find any specific examples of how this is done. Any ideas? Thanks

Well that is good to know. seems like they are starting to pick back up on getting things implemented/fixed so hopefully we will get something soon.

Ok thanks very much. Yes confirmed the mouse wheel works and yes it is slow. Hopefully they fix it and enable hotkeys soon so I can map them to my rotary encoder in my pit.

When I turn the CRS knob on a given waypoint, the CRS line does not rotate 360 degrees. It stops rotating after 30-60 degrees. Rotating the other way also has same issue. What I have just noticed is that the limit seems to change each time you rotate it back and forth. Sometimes it allows you to rotate more and sometimes its only a few degrees. I am using the mouse (since there no hotkeys) and verifyed all other knobs rotate fine. I have tested this on the ground while stationary to confirm its not related to movement. has anyone run into this? Thanks

Does Anyone Have an update on the CRS mapping?? It would be much appreciated. Thanks

Thanks for pointing me in the right direction cowboy, I had not been able to find other posts with similar issues. At least now I know I am not alone. Thanks again.

I have been exporting my MFCDs to an external monitor for a long time with no issues. With the implementation of the HUD repeater function, I am not able to see that on my exported display. To be clear- All of the other MFCD displays still show up on the exported monitor as expected except the HUD repeater function which is strange. Has anyone else run into this? Thanks

Just to provide an update, even with the latest patch I am still not able to either manually start or auto start the hog. I am following my checklists as normal but once I get to the point where I need to put the left throttle to idle to start the left engine, it just sits there and doesn't spin up. I get the same result when I try doing it through auto start. Has the startup checklist changed in the last six months? I suspect not, especially since auto start doesn't work, but figured I would ask.

On the latest openbeta version (as of todays date), I can not get the left engine to start. Checklist is followed to the letter, Ralt Home to start the engine, the throttle moves, but nothing happens. I thought it was me until i tried doing an autostart and going back through the startup tutorial and it fails in both of those cases as well. Assume this is a bug but havent seen anyone else with the issue. Any thoughts?

Thanks very much, that did the trick. Appreciate your help.

Help- I am just getting back into A10C and the lua file changes that used to allow me to export the CDU to an external monitor are no longer working. My MFCD exports still work as always but the CDU is not. Below is the modified version of the CDU_init.lua file that always worked for me. I have searched forums for days and have not been able to find any recent information about CDU exporting in 2.5 so any help would be appreciated. Thanks!! --------------------------------------------- dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") indicator_type = indicator_types.COMMON purposes = {render_purpose.GENERAL} try_find_assigned_viewport("CDU") dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON dofile(LockOn_Options.script_path.."CDU/indicator/CDU_pages.lua") init_pageID = id_CDU_Pages.CDU_PAGE_OFF CDU_preinit_files_path = LockOn_Options.script_path.."CDU/Indicator/Preinit/" page_subsets = {} dofile(LockOn_Options.script_path.."CDU/indicator/CDU_subsets_init.lua") ---------------------- pages = {} pages_by_mode = {} clear_mode_table(pages_by_mode, 10, 10, 29) function get_page_by_mode(master, L2, L3, L4) return get_page_by_mode_global(pages_by_mode,init_pageID,master,L2,L3,L4) end dofile(LockOn_Options.script_path.."CDU/indicator/CDU_pages_init.lua") use_parser = false dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON used_render_mask = "interleave.bmp" __________________ CPU:i7920 @2.67GHz overclocked to 3.25Ghz Video:ATI HD5780 Single Monitor Ram:8 GB DDR3 OS: Win7 64bit Equipment:TrackIR4, Buttkicker2Gamer,CH ProFlight Pedals, Saitek X65 Controller

Help- I am just getting back into A10C and the lua file changes that used to allow me to export the CDU to an external monitor are no longer working. My MFCD exports still work as always but the CDU is not. Below is the modified version of the CDU_init.lua file that always worked for me. I have searched forums for days and have not been able to find any recent information about CDU exporting in 2.5 so any help would be appreciated. Thanks!! --------------------------------------------- dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") indicator_type = indicator_types.COMMON purposes = {render_purpose.GENERAL} try_find_assigned_viewport("CDU") dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON dofile(LockOn_Options.script_path.."CDU/indicator/CDU_pages.lua") init_pageID = id_CDU_Pages.CDU_PAGE_OFF CDU_preinit_files_path = LockOn_Options.script_path.."CDU/Indicator/Preinit/" page_subsets = {} dofile(LockOn_Options.script_path.."CDU/indicator/CDU_subsets_init.lua") ---------------------- pages = {} pages_by_mode = {} clear_mode_table(pages_by_mode, 10, 10, 29) function get_page_by_mode(master, L2, L3, L4) return get_page_by_mode_global(pages_by_mode,init_pageID,master,L2,L3,L4) end dofile(LockOn_Options.script_path.."CDU/indicator/CDU_pages_init.lua") use_parser = false dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON used_render_mask = "interleave.bmp"

I have not been able to get this straight in my head and am hoping someone can clarify for me.....if you have a TPOD mounted (with all its features fully working), then isn't the DMT on the Harrier redundant for targeting? I guess the DMT would still be needed for FLIR, but other than that, could you basically disable the DMT and just use TPOD?

I may have fixed my own problem, which may or may not be related to the issues in this thread, so I will go ahead and describe in case it is a help to anyone. My issues was the gun sight was jumping wildly across the hud and would never get a solid lock on the A2A target which made using guns nearly impossible. I finally figured out that by dialing the Radar Range Sweep Knob back about 50%, the gun sight is now steady and I get a good lock on the target. Everyone else may already know this, but this was a major frustration for me which was killing the A2A experience.

Yes it is really really tough. If this is an accurate depiction of the F86 air to air guns, I am amazed they shot any Mig15's down in Korea. Hopefully just a bug which will get corrected....or I need a lot more practice.

Thanks for the quick reply. That is a bummer. So is the lack of ATC just something that I am hoping for or do other people feel the same way?

ATC in DCS World 2.0 I have looked for some info on the forum but have had no luck, so I am hoping someone can comment...... With all of the improvements coming to DCS World, I am surprised no one is talking about (or asking for) improvements to the ATC system. Is this correct or am I missing something? As great as DCS world is, AI ATC has never gotten any love for as long as I can remember. Any info is appreciated!! thanks

For two days I have had issues with the 1.2.3 update freezing at about the 25% mark when downloading. It takes only 10-15 seconds to get to that point, but then sits for 30-60 minutes before giving an error stating something to the effect that user cancelled request (which i didnt) Suprising that I havent seen any similar problems listed, so maybe I am the only one. Any suggestions? Help Please. Would really like to get my hands on 1.2.3 Thanks

I can also confirm I have had this issue for awhile. Once every 20-30 seconds there will be a brief freeze, then back to its normal 45-60 fps. Does not seem to matter whether you are on the ground or at 10000 feet. I have an ATI 7850 card installed. Have not found a fix for it yet either.

+1 to that. Worked for me as well