USAFMTL

That answered most however the problem is after the CDU I can's get nothing else to show up. _ = function(p) return p; end; name = _('Export example'); Description = 'Export example'; Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.6; } } ED_A10C_LEFT_MFCD = { x = 1980; y = 600; width = 410; height = 410; } ED_A10C_RIGHT_MFCD = { x = 3370; y = 600; width = 410; height = 410; } ED_A10C_CDU = { x = 3370; y = 200; width = 420; height = 324; } ED_A10C_RWR = { x = 1980; y = 200; width = 178; height = 178; } ED_A10C_CMSP = { x = 2550; y = 200; width = 300; height = 300; } ED_A10C_CMSC = { x = 2100; y = 200; width = 300; height = 300; } UIMainView = Viewports.Center

Pete I sent you a PM. I'm almost there, just need a little more help.

Thanks Pete!!!! Wish me luck.

Anyone.....please....... :D

Here it comes...the Flankerwhining.....so in a patch they will cut the nuts off the F-15 and the SU-27 will be the uber plane again, then the F-15 crowd will complain, and the cycle repeats. One of the reasons I hardly played the sim was because the F-15 has always 2nd fiddle to the Flanker, that is why you have servers with all Flankers etc.

I will check that out when I off duty. In regard to my problem. Im still a newb to all this but am I supposed to put info in the parenthesis? Or just copy and paste? Sorry for being a pain.

What is this Helios I keep reading about? I'm still stuck though.

Well I got my MFCD's et up but havign a hell of a time trying to get the DCU and the RWR to show. Here is my CDU dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON purposes = {render_purpose.GENERAL} local x_size = 1 local y_size = 1 function update_screenspace_diplacement(zoom_value) local default_width = 0.5 * LockOn_Options.screen.height + (64 * zoom_value) if default_width > LockOn_Options.screen.height then default_width = LockOn_Options.screen.height end if default_width > 0.5 * LockOn_Options.screen.width then default_width = 0.5 * LockOn_Options.screen.width end local default_height = (y_size/x_size) * default_width local default_y = LockOn_Options.screen.height - default_height local default_x = LockOn_Options.screen.width - default_width dedicated_viewport = {default_x,default_y,default_width,default_height} dedicated_viewport_arcade = {default_x, 0 ,default_width,default_height} end update_screenspace_diplacement(0) function set_full_viewport_coverage(viewport) dedicated_viewport = {viewport.x, viewport.y, viewport.width, viewport.height} dedicated_viewport_arcade = dedicated_viewport purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW, render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always 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(Dave) if f then setfenv(f,env) pcall(f) local vp = nil vp = env.CDU_SCREEN if vp ~= nil then dbg_print("ok we have directly assigned viewport to MFCD\n") set_full_viewport_coverage(vp) end end 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" -------------------------------------------------------------------------------------------- Here is my RWR 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("RWR_SCREEN") ---------------------- rwr_symbols_bound = 0.027 -- coeff to limit indication on RWR when symbol can't be place on RWR entirely -------PAGE IDs------- id_Page = { PAGE_OFF = 0, PAGE_MAIN = 1, PAGE_BIT = 2 } id_pagesubset = { COMMON = 0, MAIN = 1, BIT = 2, } page_subsets = {} page_subsets[id_pagesubset.COMMON] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_COMMON_page.lua" page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_MAIN_page.lua" page_subsets[id_pagesubset.BIT] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_BIT_page.lua" ---------------------- pages = {} pages[id_Page.PAGE_OFF] = {} pages[id_Page.PAGE_MAIN] = {id_pagesubset.COMMON, id_pagesubset.MAIN} pages[id_Page.PAGE_BIT] = {id_pagesubset.COMMON, id_pagesubset.BIT} init_pageID = id_Page.PAGE_OFF use_parser = false --- master modes A10C_ALR69V_OFF = 0 A10C_ALR69V_MAIN = 1 A10C_ALR69V_BIT = 2 ------------------------------------ pages_by_mode = {} clear_mode_table(pages_by_mode, 2, 0, 0) 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 pages_by_mode[A10C_ALR69V_OFF][0][0][0] = id_Page.PAGE_OFF pages_by_mode[A10C_ALR69V_MAIN][0][0][0] = id_Page.PAGE_MAIN pages_by_mode[A10C_ALR69V_BIT][0][0][0] = id_Page.PAGE_BIT opacity_sensitive_materials = { "font_RWR", "INDICATION_RWR" } ----------------------------------------------------------------------------------- Here is my monitor setup _ = function(p) return p; end; name = _('Dave'); Description = 'Left and Right MFCD on the right monitor' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.6; } } LEFT_MFCD = { x = 1980; y = 600; width = 410; height = 410; } RIGHT_MFCD = { x = 3370; y = 600; width = 410; height = 410; } CDU_SCREEN = { x = 2100; y = 300; width = 420; height = 324; } RWR_SCREEN = { x = 3000; y = 300; width = 178; height = 178; } UIMainView = Viewports.Center -------------------------------------------------------------------------------------- I want to add the CMSC too. So here I am stuck.....

Thanks Grimes, I totally forgot to look there.

Is it possible to move the pilot log from one install of A-10C to another computer with it installed? Also where is said log located if it is possible?

Its to the left of my main monitor. I had my MFD on my laptop monitor (using command strips) and it worked good but I decided to go bigger. I mean its no big deal I could play the move, check and see game. Just wanted to get a head start.

Does anyone have there Cougar MFD's on a 23 Inch monitor? If you have them in the upper corners can I see your positioning numbers? Also I want to add other displays (like the CDU etc) on the same monitor, could I also maybe see that set up as well? Thank you all.

I got a feeling its going to be out this week. Ok I can hope.....

I glad the F-15C got special treatment. I don't fly the Russian fighters anyway....I just shoot them down. The F-15C the worlds largest distributor of MiG parts in the world. :D Joking aside, never been a big Flanker fan, but I love the Mig-29.

My one big hope is that the missiles are fixed like they stated. Currently as many know the AIM-120C blows goats. Its sad when I get a better PK with the Great White Hope than with the Slammer. The AIM-120C, C-5 and soon the D are the best AHM's in the world. Period, the runner up is the R-77 but it doesn't have the ECCCM, yes that is 3 C's........ the new AIM-120's have. I would hope that this is fixed. Other than that I am good with what FC3 will have. I really like the fact that its integrates with DCS World. More plane, bigger theater and with Nevada coming out....Red Flag time. Bro's we are getting back to the golden age of simming again.

Yeah good point but since we have the A-10C which came out in 2005 maybe there is hope. If not, no big deal just a thought.

I wonder if the AIM-9X will be in it and the JHMCS, considering the time frame.

My new favorite quote...Pyro says..... "Join me next time for another great episode of "Blowing Stuff Up (With Math)"

For those that dont know me I used to make Campaigns and missions sets for Flanker 2 and LOMAC. I think some were added to the LOMAC release or was it an update, I think. Have to check...that's not imporant. Sorry Im rambling. Anyway the reason I say this that some of my campaigns were dead set on being close to "real life". By that I mean the story lines I like to use. I was thinking about making a missions set for the P-51D in which your unit is assigned a CAS role to stop Russian convoys from getting to their forces. The convoys are escorted by Mi-24's, which a P-51D going after is much much fun. Yes it has zero basis in reality but would it be worth putting together or have I just gone off the deep end here?

http://www.checksix-fr.com/downloads/DCS/BlackShark/Docs/DCS%20BS_How%20adding%20custom%20skin.pdf

Disregard I finally found it...

Does anyone have that PDF tutorial on installing skins manually? Can someone assist? Thanks

Boresight:The pilot flies along the planes longitudinal axis onto the target or if a target crosses the same axis, the radar locks on. WVR: Within visual range mode, in other words you're in a knife fight. This is the reason why the F-15 was made, because it was thought an F-4 would never have to engage in this realm. However see Vietnam War for that oversight. FLOOD: This mode puts the radar in a broader acquisition mode. It doesn't lock the AIM-7 for you but you can use it to home in on any taget painted by the scan. VS: Vertical Scan mode, the radar scans the airspace in front of it to a beam of 7.5 degrees wide and –2 to 50 degrees vertically. There are 2 bars displayed on the HUD and you need to get a target in between those lines to acquire a target. AACQ: I use this for guns mode, where it locks the target up and you can get a quicker firing envelope. HOJ: Home on Jam, just like it says, is useful for when an aircraft is beginning to jam to confuse the missiles radar. In that case the radar switch's modes to lock onto the source of the jamming. This mode is very unreliable though as it has to go through a electronic gauntlet to get to a target. The theory is though that with the missile is close enough that it will burn through the jamming and acquire the target and kill it. I am hoping this what you were asking for in the first question.

MadTommy Thank you for the instructions. Worked like a charm and now I have my MFCD's on another screen and its working like a champ.

I have my MFCD's in A-10C on another screen. I want to do the same for my F-15 and A-10 in FC2. I swear i saw somewhere you could do it but I can not seem to find it. Can anyone point me in the right direction? Thanks all.