icemaker

yes it's all helios in his pannel but indicators that are from dcsw

I have found a way to create all indicators of DCS viewports like MFCD. As you can see in the screen shot it's possible to create viewports for all the DCSW Indicators. Here is the way to do that : - First go to S:\DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit - Then go to the indicator folder you want to use (Eg : AN_ALR69V\indicator - then open the init.lua file of your indicator (Eg : AN_ALR69V_init.lua here) - find this line : indicator_type = indicator_types.COMMON-And just paste below this code : [color=Red]-- Code below is used for the rendering when no viewport has been created[/color] purposes = {render_purpose.GENERAL, [color=DeepSkyBlue]-- Rendering in 3D View[/color] render_purpose.HUD_ONLY_VIEW,[color=DeepSkyBlue] -- Rendering In HUD only View[/color] render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, [color=DeepSkyBlue]-- Rendering in External View[/color] render_purpose.SCREENSPACE_INSIDE_COCKPIT} [color=DeepSkyBlue]-- Rendering in In cockpit view but NOT in 3D cockpit [/color] [color=Red]-- End of rendering configuration[/color] screenspace_scale_initial = 3; screenspace_diplacement = {0,0} local x_size = 1 local y_size = 1 function update_screenspace_diplacement(zoom_value) screenspace_scale = screenspace_scale_initial + zoom_value; if screenspace_scale < 1 then screenspace_scale = 1 end local screen_height = 2.0; local screen_width = screen_height * LockOn_Options.screen.aspect; local scaled_width = SelfWidth * screenspace_scale local scaled_height = y_size * scaled_width -- for indicator all sizes is function of width scaled_width = x_size * scaled_width screenspace_diplacement = { 0.5 * screen_width - 0.5 * scaled_width, -0.5 * screen_height + 0.5 * scaled_height} screenspace_diplacement_arcade = {screenspace_diplacement[1], 0.5 * screen_height - 0.5 * scaled_height} end update_screenspace_diplacement(0) function set_full_viewport_coverage(viewport) local w = LockOn_Options.screen.width local h = LockOn_Options.screen.height local a = LockOn_Options.screen.aspect local x = (-1.0 + 2.0 * (viewport.x / w)) * a local y = 1.0 - 2.0 * (viewport.y / h) local width = (viewport.width / w) * a local height = viewport.height / h local scl_hgt_K = y_size * SelfWidth -- size always function of SelfWidth local scl_wdt_K = x_size * SelfWidth -- size always function of SelfWidth screenspace_scale_x = 2.0 * width / scl_wdt_K screenspace_scale_y = 2.0 * height / scl_hgt_K screenspace_diplacement = {x + width, y - height} screenspace_diplacement_arcade = screenspace_diplacement[color=Red] -- The code below is used for rendering When you use viewports comments are same as above for rendering[/color] purposes = {render_purpose.HUD_ONLY_VIEW, --render_purpose.GENERAL,[color=DeepSkyBlue] --Uncoment this line by removing the "--" to render in 3D cockpit.[/color] render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always [color=Red]-- End of rendering configuration[/color] render_target_always = true end -- try to find assigned viewport local multimonitor_setup_name = "Config/MonitorSetup/"..get_multimonitor_preset_name()..".lua" local env = {} env.screen = LockOn_Options.screen local f = loadfile(multimonitor_setup_name) if f then setfenv(f,env) pcall(f) local vp = nil vp = env.[color=Red]RWR_SCREEN[/color] if vp ~= nil then dbg_print("ok we have directly assigned viewport to CDU\n") set_full_viewport_coverage(vp) end end -Change the red value name to set your viewport Name -Go to \Config\MonitorSetup\YourMonitorFile.lua - And add Viewport like this : RWR_SCREEN = { x = 1000; y = 1245; width = 170; height = 170; }Enjoy!!! No cockpit avionics display render and ready for export in DCS-A10 1.1.1.1 and a Example LUA.zip

My answers are : 1) Of course YES 2) YES 3) If i make some i will And if you need help i'm your man...

Outer Dimensions 116.00 (L) Ч37.00 (W) Ч18.70 (H) ±0.20mm Display size 70.80mm 11.50mm Number of Characters 20 characters Ч 2 lines Character Format 5*7 Dot Matrix with Cursor Character Size (excluding cursor) 2.40mm x 4.70mm Character Pitch 3.6(H)/6.1(V)mm Dot Size 0.40mm Ч 0.50mm Display Color Blue-Green (peak 505nm)

http://www.sureelectronics.net/goods.php?id=1097

+1

Thanks...:thumbup:

Not sure you have enough buttons managed by the bodnard's card... i planned to use USB keyboard matrix to use with UFC and CDU...

great panels !! Is there any possibility of backligthing of panels and buttons?

Edited my previous post, i have updated the OnOffMom function. All my panels works. EMER FLOOD has been intentionally deactivated in clickabledata so i use it for cdu on off.

Finally it works! here the new lie to add in siocConfig.lua depending on type of mom button [511] = {OnOffMom, 39, 6, 7, 1} -- For buttons With -1;1 range [511] = {OnOffMom, 39, 6, 7, 0.5} -- For buttons with 0;1 range And the code to add in ExportSupport.lua function OnOffMom(pValue, pDevice, pNumber1, pNumber2, pType) local pVal, PNumb if pType == 0.5 then if pValue == 1 then pNumb = pNumber1 pVal = 1 elseif pValue == 2 then pNumb = pNumber1 pVal = 0.5 elseif pValue == 3 then pNumb = pNumber2 pVal = 0 else pNumb = pNumber2 pVal = 0.5 end end if pType == 1 then if pValue == 1 then pNumb = pNumber1 pVal = 1 elseif pValue == 2 then pNumb = pNumber1 pVal = 0 elseif pValue == 3 then pNumb = pNumber2 pVal = -1 else pNumb = pNumber2 pVal = 0 end end GetDevice(pDevice):performClickableAction(pNumb + 3000, pVal) end And the code for SIOC Var 0511, name Canopy Var 1010, name Canopy_Open, Link IOCARD_SW, Input 16 { IF &Canopy_Open = 1 { &Canopy = 1 } IF &Canopy_Open = 0 { &Canopy = 2 } } Var 1011, name Canopy_Close, Link IOCARD_SW, Input 15 { IF &Canopy_Close = 1 { &Canopy = 3 } IF &Canopy_Close = 0 { &Canopy = 4 } } Thanks for help gadroc

thanks a lot Gadroc :notworthy: i'll investigate this.

Here are my first pannels : the AHCP is not at the good sizes because i dont know the good ones. but it's fully operational, the elec power is the next to be configured in DCS and then the Fuel Panel.

no problem take your time :thumbup:

any news gadroc?

thanks gadroc :thumbup:

Hello all, I started the pitbuilding adventure! and it's not an easy thing for me! I use IOCards and SIOC to manage inputs/ouputs from DCS the ACHP is fully functionnal but i run into problems with some switchs who used the momentary position, like the canopy open/close switch. i found this in the clickabledata.lua but i cant figure out how to manage this! i have tried with simplerotary and simpleswitchbutton but nothing works! in the sim this button never get back to center position, it goes up or down but never stops in middle position even if i place my real switch in middle position. I see this buttons works fine in Helios but i dont know how? another thing i have found is that to open using sim switch it sends button 6 1 to open and 0.5 to stop and button 7 0 to close and 0.5 to stop

F-18E for multirole and carrier operations :thumbup:

Yes Balkans could be a good place to play! :thumbup:

very interesting pitbldr! Check MP!

You're right teej, but it seems the problem comes when you plug at the same time a peripheral that uses a lot of power from usb (Scanner, Hardrive not self powered...) the USB chipset can't handle to manage the power asked and the Throttle doesn't supports the power variations.

Maybe wha have a clue! Users tha have probles with throttle what motherbord have you? In C6 we have found 4 ASUS P5Q mobos an 1 ASUS P5B

yeah you are right thanks anyway :thumbup:

Hy Flim nice work! Can you tell me where have you found the pannels dimensions? I want to start my home made pit but cant find the cocpit pannels dimensions. Thanks

Dethmagnetic, just wait a fiew days the new T.A.R.G.E.T Release Candidate that will come with new functionalities that are specially designed for that you want to do...