mikemadmax20

Hi again Andre: Thanks for your quick reply. I guess I'll go with BK Gamer 2 and see how I can somehow attach it to my Air Force Gaming Seat. Thanks again, Mike "Mad Max"

Hi Andre: It's been a while since we last connected. As you may (or may not recall), I purchased my KW-908 a couple of years ago. A fantastic product (although I had to eventually replace my power module). The sense of immersion it adds to my flight sim is incredible. Also, here's a shout out to f410. I also acquired the Simshaker for Aviators software when it became available. Together they both make my DCS F/A/-18 rock. I was initially flying BMS's Falcon until the early release of the F/A-18. Now I'm back with DCS and exclusively flying the Hornet. I'd like to kick it up a notch and add a buttkicker. I have an Air Force Gaming seat and would like to get you guys advice on which one to get - The Buttkicker Gamer 2 or, the Buttkicker Simulation Kit. I don't believe my AF Seat will accommodate the BK Gaming 2. Your thoughts would be appreciated. BTW, I plan to your FSE Vibrating Pad in March - no later than April. Best regards, Mike "Mad Max"

Hi Hansangb: Quick note: My MDI PB's (Left, Right and, AMPC) map and correspond exactly to my Three Cougar F16 MFD PB's (i.e.: Left MDI PB 1 --> JOY_BTN1, etc.). I see from the above, there is a variant in the MDI PB to JOY_BTN mapping (i.e.: Left MDI PB 1-->JOY_BTN16). That's completely different from my F/A18 Control dropdown Setting's display. What gives - Am I missing something? Thanks in advance for your guidance.

My thoughts exactly.

Great design concept which would be a fantastic product offering to the serious flight simmer and, car driving enthusiasts, alike. I'd also be one of the first in line to purchase - whether it be as a patented/design plan single-user sale (for the user to independently build) or, through a manufacturer selling the finished product to the masses. Either way, in my view, you should move forward with getting your integrated-g-seat into the market at your earliest possible convenience. Again, a great product. BTW, also love your Hornet Pit. Best wishes and luck, Mike "Mad Max" (DCS F/A-18 Novice Driver)

Hi Hollywood: Just purchased VAICOM PRO this AM and it appears that I'm getting an incomplete download from the website - missing the .vap profile. Any advise to offer? Regards, Mike "Mad Max"

Hi WAGS: Any recent news on TM's Hornet FSC?

MAD Max's Hornet Setup

Hi Capt Zeen: I'm in the process of setting up a modest Hornet pit using multiple monitors. (see my modest pit photo below) So, a quick question. Do you have separate HELIOS image panels available for the following: 1. Left "FIRE EXTGH, A/A, A/G and, Master Arm" panel; 2. Left " JETT STATION SELECt, CTR, LI RI, LO, RO, Nose, Left, Right" LG panel; 3. Right "IR COOL Oride, HMD and, SPIN RCVY" panel. Your help would be tremendous. BTW, your Hornet profile is fantastic - great work. Thanks in advance, Mike "Mad Max"

Thanks again SARGE. Yeah, you're right. HELIOS pops with a Touch Screen which I'll use with my remaining three touch screens. Sound advice regarding AMPCD. I'll follow your suggestion and disable the map until I need it. Map is great for visual location/sit awareness. But, as I learned early on as a Mud-Marine - master shooting an azimuth on your hand held compass. Additionally, I'll look into font color options.

AMPCD Export to Snd Monitor Hi Feefifofum and SARGE55: I followed your step-by-step guidance and, am elated to report - JOY to the World this Holiday Season. I finally got AMPCD to render within my 3rd TM Cougar MFD. Also changed the Shader Draw Line parameter from false to true in the associated AMPCD indicator lua with great results (corrected blurry font). "See Photos below" However one additional question. Since the green font kinda gets lost in the sauce on the moving map - how can I change the font color to maybe: Black, Blue or, Red for better contrast? Now onto further layout development with placement of EFIE, RWR, HSI and other standby gauges on 2nd monitor along with a Left & Right panel build using Capt Zeens's HELIOS profiles/images to populate my 3 remaining monitors. I was able to accomplish this challenging task in my previous modest cockpit builds for DCS's A-10 and BMS' Falcon (see attached photo) using a combination of HELIOS and YAME profiles and image extractions. I'm confident I can replicate it within the F18 model. I've been waiting with bated breath for a truly immersive F/A-18 Hornet simulation since my early days with Jane's F/A-18, DI's Super Hornet and, Graphsim's Operation Iraqi Freedom. ED has answered my prayer. The DCS F/A-18C will now be my goto aircraft. Also can't wait for TM's Hornet Flight Stick release - I'll be one of the first to anti up. Thanks again guys for your gracious support and in closing _ Merry Christmas to All and, To All a Good Night. Happy Holidays. :pilotfly:

Secondary is a LG 32" @ 1920x1080

Hi again Sarge: Thanks a bunch for working on this with me. You're providing me with a clearer understanding of the mod process. Its really appreciated. I've implemented your AMPCD lua, along with your monitor setup lua (minius Harrier). Still no joy on AMPCD placement on second monitor. Quick question though. Do I have to pass these lua's through JSGME or OvJME first? Because even though I've changed the scripts to mirror your's, my F18C saved lua is not showing up in my in game options monitor setup pulldown. BTW, I'm also using Notepad ++. And we've got something else in common. I'm also north of sixty, kissing 68. Note: My primary is a Dell Curved 34" @ 3440x1440 and, secondary AMPCD_init.lua FA18C.lua Thanks again, and hope to chat soon.

Hi Sarge55: I believe you've peg it for me. After I made the change in my Monitor Setup, I not only didn't get the AMPCD exported to me second monitor, I lost the in-game cockpit AMPCD render as well. To be frank, I'm throwing sh.t on to wall and hoping it sticks. So, if I may put the beg on you - would you kindly advise exactly what changes I should make. And equally as important - where the changes should be made (both in my AMPCD lua and Monitor Setup lua). FeeFiFoFum has been a tremendous help but, I'd appreciate your further input as well. The more eyes on this the better. Thanks in advance. Keep em Fly'n.

In AMPCD lua I've changed line 29 to reflect: writeParameter("MDG_init_DEFAULT_LEVEL") I don't know where that emoji came from.

And here's my Monitor Setup lua: --***DO NOT MODIFY THESE COMMENT LINES*** --A10CVirtualCockpitServer v0.0.0.0 --LOCATION Config\MonitorSetup --HOOKTO --Monitor lua _ = function(p) return p; end; name = _('FA18C Virtual Cockpit Server'); Description = 'Setup for FA18C Virtual Cockpit Server MFCD and AMPCD Exports.' Viewports = { Center = { x = 0; y = 1; width = 3440; height = 1440; viewDx = 0; viewDy = 0; aspect = 2.9; } } LEFT_MFCD = { x = 1257; y = 1758; width = 312; height = 312; } RIGHT_MFCD = { x = 2177; y = 1730; width = 312; height = 312; } --AMPCD CENTER_MFCD = { x = 1405; y = 1770; width = 315; height = 312; } UIMainView = Viewports.Center

OK, here's my AMPCD lua: dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/MDG_materials.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("CENTER_MFCD") opacity_sensitive_materials = { MDG_font_name(MDG_SELF_IDS.HI), MDG_material_name(MDG_SELF_IDS.HI), "MPD_DMC_OUTLINE", "font_MPD_DMC_outline", "font_MPD_DMC_main", } -- Parameters handling functions dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/InitParams.lua") indicator_type = indicator_types.COMMON -- for test purposes HUD only added purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.5 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true -- Parameters to customize common symbology properties writeParameter("MDG_init_specifics", LockOn_Options.script_path.."Multipurpose_Display_Group/AMPCD/indicator/AMPCD_specifics.lua") writeParameter("MDG_init_DEFAULT_LEVEL", 8) -- page specific for the indicator, implements indicator border/FOV BasePage = LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Pages/MPD/MPD_base.lua" -- Cautions/Advisories and MENU label IndicatorSpecificPage = LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Pages/MPD/CautAdvAndMenuPage.lua" dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Pages/MPD/MPD_AdvisoriesDefs.lua") dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Common_init.lua") -- for test purposes HUD only added --ViewportHandling dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") ---------------------------------------------------------------------- local w = LockOn_Options.screen.width; local h = LockOn_Options.screen.height; if LockOn_Options.screen.oculus_rift then local ui_x,ui_y,ui_w,ui_h = get_UIMainView() w = ui_w; h = ui_h; end local size = 0.5 * h if size > h then size = h end if size > 0.5 * w then size = 0.5 * w end dedicated_viewport = {0.5 * w - 0.5 * size,h - size,size,size} dedicated_viewport_arcade = dedicated_viewport ---------------------------------------------------------------------- try_find_assigned_viewport("CENTER_MFCD")

And again, thanks a bunch for helping me work this out. I realize that your time must be at a premium. But extending your expertise is really appreciated. As soon as I get this under my belt my belt, I'll pay it forward as well. A band of brothers we are. Marine Vet here.

Also, it seems that you're suggesting that viewport("F18CENTER") callback is the way to go as opposed to viewport("F18_AMPCD) in my script above.

Once I have a workable convention for the AMPCD script, I'm confident I'll get the RWR and IFEI as well. I just need a correct base point to work from.

What should I cut and replace with a working script?

Yep. You got that right. Now what.

BTW, here's my setup.

Thanks for the quick response FeeFiFoFum. Now that's what I call a clear, definitive, detailed and, unambiguous "HOW TO" directions. However, a couple of quick questions: On which line do I insert the "dofile" ? Please take a look at my AMPCD lua below: dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/MDG_materials.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_AMPCD") opacity_sensitive_materials = { MDG_font_name(MDG_SELF_IDS.HI), MDG_material_name(MDG_SELF_IDS.HI), "MPD_DMC_OUTLINE", "font_MPD_DMC_outline", "font_MPD_DMC_main", } -- Parameters handling functions dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/InitParams.lua") indicator_type = indicator_types.COMMON -- for test purposes HUD only added purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.5 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true -- Parameters to customize common symbology properties writeParameter("MDG_init_specifics", LockOn_Options.script_path.."Multipurpose_Display_Group/AMPCD/indicator/AMPCD_specifics.lua") writeParameter("MDG_init_DEFAULT_LEVEL", 8) -- page specific for the indicator, implements indicator border/FOV BasePage = LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Pages/MPD/MPD_base.lua" -- Cautions/Advisories and MENU label IndicatorSpecificPage = LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Pages/MPD/CautAdvAndMenuPage.lua" dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Pages/MPD/MPD_AdvisoriesDefs.lua") dofile(LockOn_Options.script_path.."Multipurpose_Display_Group/Common/indicator/Common_init.lua") ------------------------ added by Capt Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_AMPCD") ------------------------------------- end of added by Capt Zeen -- for test purposes HUD only added --ViewportHandling dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") ---------------------------------------------------------------------- local w = LockOn_Options.screen.width; local h = LockOn_Options.screen.height; if LockOn_Options.screen.oculus_rift then local ui_x,ui_y,ui_w,ui_h = get_UIMainView() w = ui_w; h = ui_h; end local size = 0.5 * h if size > h then size = h end if size > 0.5 * w then size = 0.5 * w end dedicated_viewport = {0.5 * w - 0.5 * size,h - size,size,size} dedicated_viewport_arcade = dedicated_viewport ---------------------------------------------------------------------- try_find_assigned_viewport("CENTER_MFCD")

Finally got Left and Right MFD's (DDI's) working on my 2nd monitor and placed just where I want them. However, I can't export The AMPCD within my 3rd TMMFD. I've read a ton of posts but, nothing seems to work. I'm trying to export the AMPCD outside of Helios as I've done with the L & R DDI's using JSGME. Also want to follow with IFEI and RWR placements on 2nd monitor - outside of Helios. I plan to populate the rest of the instrument panels using Capt. Zeen's Helios profile as soon as I crack the AMPCD/IFEI/RWR export issue. Could use some clear guidance here. Thanks in advance for your help Guys. You're the best.