0utLAW

Yeah, I've noticed in past updates(not sure about new ones) that when I apply the update my exports don't work and I need to go through the process of exporting them. I assume I need to back up my monitor export lua, and the individual viewport folders i.e. CMCS, CDU, both MFCD's and so forth. Any other folders/files you recommend in backing up for this issue as well?

Seems like everytime there's an update we need to go through and setup the viewports to be displayed on secondary on monitors.(I haven't done the latest update in fear of having to go through this process yet again. Not sure if this has changed or not.) Would it be possible/how hard would it be, to have an option in the game options menu to be able to toggle these on or off? What I mean by this is in the game options menu, have a toggle that you can turn on or off to export the MFCD's and other items you would want on a secondary monitor. Then, if you check the box for that item it would display on your screen and you would be able to move and resize the MFCD's and other items to make easier to work with things like Helios. Just a suggestion.

Hey guys and gals, it's been a while and I'm glad to be back. I've been kicking around the idea of building a Desk/simpit out of extruded aluminum. I was wondering if anyone has experience using this material and what I might want to take into consideration before buying this material(metric vs standard, hollow vs solid, single vs double...) Any tips, ideas, PHOTOS, of pits and the use of this product would be more than welcome.

Thanks for your posts guys, but I don't they cover what I'm trying to accomplish here. I would like to have the items for the A-10C found in the Export example file to be displayed on my secondary touchscreen while running Helios.

So does anyone have their viewports working with the latest update 1.2.10.32275? If so, what and how did you do it? :)

I recently updated to 1.2.10 and now my viewports no longer work. This is the method I used when I was running version 1.2.8(I think). http://forums.eagle.ru/showpost.php?p=1541311&postcount=68 Since the update, I have overwritten the Config, Mods, and Scripts directories within my Program Files\Eagle Dynamics\DCS World directory with the directories from the 1.MFCDs in Cockpit ON directory. I then replaced the Export example.lua file in the MonitorSetup directory with my modified one with the same name. I have attached my custom Export example.lua file and the zip file I used to try to get the viewports exported. Anything you can think of or if there is a working method for exporting viewports for version 1.2.10 please share. Thanks All_Exports_On_in_A10C_for _DCS World_1.2.0.zip Export example.lua

Any plans for a 1.2.10 update? I just updated DCS last night and now no exports even after a reinstall of the 1.2.5 version for the exporter files.

I have 3 GroovyGameGear boards and all assigned through Helios. Check out the links in my sig for video tutorials.

This process worked for me http://forums.eagle.ru/showpost.php?...1&postcount=68

Thank you guys for not responding to my post. It forced me to take 5 minutes to search for my own darn posts and I found the answer to my problem; http://forums.eagle.ru/showpost.php?p=1541311&postcount=68 Sorry for being a spaz! :doh:

Does anyone know if this works with the latest version of DCS World 1.2.10.30996? I have also opened my DIGIT_CLK_init.lua file and pasted the following below the indicator_type = indicator_types.COMMON line. I changed the line to match the name of the indicator vp = env.DIGIT_CLK -- Code below is used for the rendering when no viewport has been created purposes = {render_purpose.GENERAL, -- Rendering in 3D View render_purpose.HUD_ONLY_VIEW, -- Rendering In HUD only View render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, -- Rendering in External View render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- Rendering in In cockpit view but NOT in 3D cockpit -- End of rendering configuration 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 -- The code below is used for rendering When you use viewports comments are same as above for rendering purposes = {render_purpose.HUD_ONLY_VIEW, --render_purpose.GENERAL, --Uncoment this line by removing the "--" to render in 3D cockpit. render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always -- End of rendering configuration 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.DIGIT_CLK if vp ~= nil then dbg_print("ok we have directly assigned viewport to CDU\n") set_full_viewport_coverage(vp) end end

My DCS Options are set as follows; Resolution= 3840x1080 Aspect Ratio= 3.5555555556 Monitors= Export example Fullscreen is unchecked

Hey guys(more specifically peterp), here we go again. I've installed a fresh copy of DCS World and A-10C and I'm using the [How To] Export ALL Indicators like MFCD via ViewPorts http://forums.eagle.ru/showthread.php?t=70716 post to configure my indicators. I have the left and right MFCDs showing correctly but none of the other indicators are moving to my second monitor. I know I'm missing one simple step that I always overlook. Here are the details of my new setup. Physical Monitor Setup Primary(Center/Main) Monitor- Acer GD235HZ 1920x1080 120hz Secondary Monitor- Hanspree HT231DPB Touchscreen 1920x1080 60hz Windows Monitor Configuration I have attached copies of my Monitor Setup lua and Digital Clock Indicator lua as some examples. Any help would be appreciated. Thanks, 0utLAW Export example.lua DIGIT_CLK_init.lua

It's in Control Panel/Tablet PC Settings/Configure, hit the setup button and follow the instructions. Easy peezy!

Thanks chichlid! You're always awesome! I'll give that a shot.

so playing around with it for a couple of minutes it looks like the touchscreen has to be set as the primary display in order for the touch ability to work on only that screen. Does anyone know if it is possible to only have it work as the secondary? If not are there any work-a-rounds?

Hey guys! It's been a while since I've been on here. I hope everyone is doing ok. I have a question about setting up a Hannspree HT231DPBU as my secondary monitor that is a touchscreen. I don't know if this is an issue or not but I've hooked up the Hannspree as my secondary monitor and when I go to select something on the screen it activates the same point on my primary monitor. Is this normal? Is there a way to only have the touchscreen work on the secondary monitor only? Also, is there any special setup when using it for my front panel in DCS? I am running Helios and exporting the front panel to the secondary monitor. Please ask for more information if needed and if I need to be more clear please let me know. Basically, I only want the touch function to work only on the secondary monitor and not active anything on my primary. For PC info please see my sig. Thanks a bunch!

Right-click desktop/Screen Resolution/Advanced Settings/Properties/Driver/ and select Disable? -OR- Device Manager/Monitors and Right-click on my current primary and select Disable?

Hey pie, what is your method for disabling and enabling your primary monitor?

Just might have to build a dedicated DCS World machine from older computer parts. :)

Also, I assume that if I make my Samsung my "Primary" screen that all my other games will open on that screen as well? :(

Correction { Center = { x = -1920; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.7; } } GUI= { x = -1920; y = 0; width = 1920; height = 1080; } UIMainView = GUI

Tony- I believe I may be looking for something more like this perhaps; { Center = { x = -1920; y = -1080; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.7; } } GUI= { x = -1920; y = -1080; width = 1920; height = 1080; } UIMainView = GUI

I guess the next question is. Before I change my monitor export lua and make my secondary my primary in windows, will this affect any of my other exports?

Also, two things. One, I would like to keep the Acer on the left and the Samsung on the right in the setup. Physically I will move the Samsung from the right position to underneath the Acer when playing A-10C. Two, did anyone notice the little project I'm working on in my Helios profile?