Greekbull

Thank You very much!!! That solved all of my problems. I was able to get a lot more stuff extracted. Here's a link to the thread: http://forums.eagle.ru/showthread.php?t=156943 Hopefully some more of you are Helios users and would like to pitch in to get a good profile going. Right now mine will just display all of the exports. But no switches or side panels.

Updated original post with a Dropbox link for the Helios Profile...

OK thought I would get a thread going and hopefully between the community we can get a good Helios profile going. I've put a couple of hours into it and have taken a Hi Res screen shot and started to modify it into a Helios profile. I plan on doing a day and night version. So far I have zero working switches but I have successfully exported the following into the profile: Radar RWR Coms Bomb Ripple quantity and interval screen Stores Management Fuel Flow I want to clean it up and will post for anyone to use. I hope some of you who know more than me can maybe get working or give me pointers on the analog gauges, tapes and switches:D Here's what it looks like so far(just have the illuminated night profile going): Edit: Ok here's a link to my profile: https://www.dropbox.com/sh/syn8qp6b7dduoh4/AAB2KyVJEGe7QWmhAPLr17Fua?dl=0 Instructions: 1.Drop the background into your helios images 2.Load the Profile and do the reset monitors to your system. Mine uses a 4K main display and a 1080P Touchscreen for Helios. So as long as you have a 1920X1080 Helios display you should have an easy time configuring. 3. I have included the .lua file for each of the items I've extracted. You can simply go to your Mods/Aircraft/M-2000/Cockpit file and drop each of those in. 4. I have also included an example of MY Monitor extract file...You will need to change this for your setup and where you want to export each display. I would suggest using one of the easy X,Y cordinate locator programs. Can be done pretty quick:) Please take this image, files, anything and run with it....This is the most I know to do so far so anyone that knows anything about the gauges, or switches please feel free to run with it:D I will load my day time when I get it going too...

I know just enough to be dangerous but I believe you point the profile to the game file...I have one profile for 1.5 and one for 2.0 that I labeled as such.

Ok I'm having issues...I'm really green with this but have been able to get it working with the A-10C and F-15C in helios... When I go to the DCSWORLD\Scripts\Aircrafts\_Common\Cockpit ---> ViewportHandling.lua I'm not seeing any file named Viewport handling in 2.0 or 1.5. Do I need to make it? I'm using a 3840x2160 main monitor and a 1920x1080 touchscreen for my instruments. Here's what I have for the files... Monitor setup specific to the M-2000: _ = function(p) return p; end; name = _('M-2000 working night'); Description = 'Right MFCD on the right and camera on the center' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 16/9; } } --////////////////////////////////////// -- Mirage 2000 = --////////////////////////////////////// Mirage_Radar = { x = 1690; y = 2626; width = 430 ; height = 430; } Mirage_RWR = { x = 2215; y = 2211 ; width = 250; height = 250; } UIMainView = Viewports.Center My VTB_init.lau file: dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON --purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW} VTB_PAGE_0 = 0 VTB_PAGE_1 = 1 VTB_PAGE_2 = 2 SRC_VTB_BASE = 0 SRC_VTB_0 = 1 SRC_VTB_1 = 2 SRC_VTB_2 = 3 local my_path = LockOn_Options.script_path.."VTB/" page_subsets = { [sRC_VTB_BASE] = my_path.."VTB_base.lua", [sRC_VTB_0] = my_path.."VTB_page_0.lua", [sRC_VTB_1] = my_path.."VTB_page_1.lua", [sRC_VTB_2] = my_path.."VTB_page_2.lua", } ---------------------- pages = { [VTB_PAGE_0] = {SRC_VTB_BASE,SRC_VTB_0}, [VTB_PAGE_1] = {SRC_VTB_BASE,SRC_VTB_1}, [VTB_PAGE_2] = {SRC_VTB_BASE,SRC_VTB_2}, } init_pageID = VTB_PAGE_0 used_render_mask = "interleave2.bmp" --default mask for TV dofile(LockOn_Options.common_script_path.."Viewpor tHandling.lua") try_find_assigned_viewport("Mirage_Radar") My RWR_init.lua file: dofile(LockOn_Options.common_script_path.."devices_defs.lua") local my_path = LockOn_Options.script_path.."RWR/" indicator_type = indicator_types.COMMON PAGE_0 = 0 SRC_RWR_BASE = 0 SRC_RWR_0 = 1 page_subsets = { [sRC_RWR_BASE] = my_path.."RWR_base.lua", [sRC_RWR_0] = my_path.."RWR_page.lua", } ---------------------- pages = { [PAGE_0] = {SRC_RWR_BASE,SRC_RWR_0}, } init_pageID = PAGE_0 used_render_mask = "interleave2.bmp" --default mask for TV dofile(LockOn_Options.common_script_path.."Viewpor tHandling.lua") try_find_assigned_viewport("Mirage_RWR") Anything you guys see me missing? Is that third file needing to be created? Any help will be hugely appreciated!!! Thanks!

This thread has instructions: http://forums.eagle.ru/showthread.php?t=156657 But I still haven't been able to get it to work yet:(

The last update Baker gave was they are getting pretty close to releasing a 1.5/2.0 version...so hopefully we'll get the use of this awesome program soon :D Baker, it looks like the Radar and RWR at least(maybe more) are exportable on the Mirage 2000C just released. Would love to see that added to your product!

Going to work on exporting today...does anyone know the labels of the other digital displays on the main cockpit and if those are exportable? Was thinking of taking a Hi Res screen shot of the main panel and cutting out holes for the radar, RWR and stores management to run on my helios monitor for the time being until someone who knows a lot more about helios than me actually builds a profile :D

General comment to Razbam and Zeus, I want to say a big thank you for releasing this and making this a Merrier Christmas:). The overwhelming majority of us aren't concerned at all about any missing functions or bugs...because we realize it's a Beta and would much rather have something to fly now than wait for a totally finished product! This wasn't in response to general reporting of bugs of course because that's helpful. But I can't believe people are mad at the condition of a Beta or comparing it to products that have been out for quite some time:D Have a very Merry Christmas!

Awesome news all around...can't wait for the F-15E hopefully the AG Radar isn't far off...and great news about the Buckeye!!!! That would've been a total waste of development time :D

Edit: awesome news Zeus thanks!

It works fine with 2.0. I have a separate profile for 2.0 that's targeted to 2.0. But other than that it works great. Would love to see Capt Zeen tackle the Mirage that releases tomorrow! That would be awesome!!!

I'm sure everyone at LNS isn't working on the MIG 21 project...so it doesn't have to come down to giving an update or not vs fixing some bugs in a Alpha..and Beta which quite frankly should be expected to have plenty of bugs... So while you might not want it...the majority of people are excited for an update!

So excited for this to release:D and of course to get Baker some well earned $(actually £ lol) for his awesome work!

Lol its hard not to...it's pretty much being in virtual development longer than the real jet took to make:D...really hope we see it next year though! Not going to hold my breath though;) My fear is ED is going to do the F-16 afterwards...which means we won't see that till like 2025 lol. But back on topic...the Tomcat will make me very happy and forget all my other wants in DCS so I'm really excited for that next year...

Really looking forward to the December update! The F-14 is the module I'm most excited for(pretty much given up on the F-18:)). Thanks for keeping us posted Cobra!:D

Awesome! So excited to use this again :D. Thanks for your efforts Baker!

Don't care about any content what so ever. Please just release and update :)

Yeah and Mid December is gone as well surprise surprise...just laziness...again not by Razbam, but by ED!

Total BS! ED lets us down again....it's a Beta...it's not supposed to be perfect!

I sure hope we can fly this weekend in the M2000...I know it's not Razbam's fault but I really hope ED can step up to the plate and please some customers. We haven't had a new combat jet in a long time..

We already have 2 too many high fidelity trainers in DCS with no released multirole fighters...for the love of God and all things Holy please no more trainers. No one wants them. We want combat aircraft!:D

Just found this thread, nice!:) Will only be running HAF skins with the M2000:D

It sounds like everything is finished for the Beta release and is likely in ED's hands to release to us...in which case it would be out of Razbam's control. I'm just speculating and reading between the lines but that would be normal. If that's the case my guess is Friday with a ED update. Guess we'll see. Thanks for the update Zeus!

Oh thank God you are back! So happy and can't wait to use your program in 1.5 and 2.0!!!! DCS was not the same game without it!!!