Leaderboard

For all that are thinking about to build a real HUD for their cockpit: I took the time to look again on a old personal problem of mine (Support to Export the HUD -Please!) - Encouraged by some postings/pictures of sleepara in this thread..http://forums.eagle.ru/showthread.....I decided to revisit this problem again (The pity is that Sleepara didn't told anything about the "how-to" ...) . And now I think I got something figured out that you can call "robust".:) Sleepara's HUD : Some important notice ahead: I assume you know what you are doing by using this instruction and you are not a novice editing lua files. If this is not the case - start your practice here:Dummies Guide for the “MonitorSetup.lua“ This HUD-view-port export will only work satisfying if you don't want to use the in-cockpit collimated HUD any-more and Have a static view/projection of the Hud-only-view ! - So If you don't have a projector for it and still want to use TrackIR: Don't waste your time !! - just don't even try to make the edits , as the in-cockpit HUD will not be collimated and usable any-more. And: Don't blame me for not making backups - and turning your installation FUBAR ! Edit: Updated this post to reflect the chages that came with DCS World 1.2.0 Here is also a file package for simple Copy'N'Paste for DCS World 1.2.0 I attached my working files Including a instruction and a demo monitorsetup-lua. >>> http://files.digitalcombatsimulator.com/en/208117/ There is maybe a more "elegant" way (if you know how - please share it with us!)- but this is what I found out up to now - and most important : It works!:) When you follow the instruction closely, the HUD can be placed anywhere inside you in-gamreselution in any size and no HUD is visibile in the HUD-only view, but the HUD-export will still stay visibile. This is how it's done : BTW: This works almost the same for the Ka-50/P-51D File path P-51D: ModsaircraftsP-51DCockpitScriptsGunsight_K14IndicatorK14_init.lua File path Ka-50: ModsaircraftsKa-50CockpitScriptsHUD_init.lua ..well , you will have to experiment with the SymbologyBox_size in the *_base_page.lua of the different modules. Do this edits to your DCS WorldModsaircraftsA-10CCockpitScriptsHUDIndicatorHUD_init.lua Change line #4 from this: indicator_type = indicator_types.COLLIMATOR to this: indicator_type = indicator_types.COMMON and add this after line #7 so you can view this export by using A10_HUD in your "MonitoSetup.lua": 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(multimonitor_setup_name) if f then setfenv(f,env) pcall(f) local vp = nil vp = env.A10C_HUD if vp ~= nil then dbg_print("ok we have directly assigned viewport to MFCD ") set_full_viewport_coverage(vp) end endNow it will look similar like this when A10_HUD is defined as a view-port. Well - some parts are still missing/cut off: To get everything of the HUD displayed you need to edit the DCS WorldModsaircraftsA-10CCockpitScriptsHUDIndicatorHUD_base_page.lua Starting at line #3 from this: SymbologyBox_sizeX = 90 SymbologyBox_sizeY_min = -215 SymbologyBox_sizeY_max = 167To this: SymbologyBox_sizeX = 160 SymbologyBox_sizeY_min = -225 SymbologyBox_sizeY_max = 225 Voilà!: Just keep in mind that the A10_HUD export will be greater than defined in you "Monitorsetup.lua" at around 20%. See the lua below - I use 602x602 as HUD-size but it covers almost all 700x700. Here is the "MonitorSetup".lua that I used for the example above . Used resolution was 1400x700 windowed. Now you only need a projector and a Fresnel lens - a glass - some time -and you have your own working HUD. Some tips to set it up and calibrate: 1.Use a pico-projector or a small bright lcd and a Fresnel-lens - so you get a linear projection of the HUD. (> focused to infinity) Display it on a 45° glass in your eyesight. 2.Than start DCS with the unedited files in HUD-Only view. Make a screen-shoot of the HUD-Only image while the HUD is visible. 3. than display this HUD-only view over the output of your "outer-world" projection. While at the same time having the export of the Hud visible. 4.Than tweak the image of the export as long as it will match absolutely with this screen-shot. Build it very sturdy so you cant move the HUD-projector. -Ready! This image is meant to give you a little idea what I'm talking about: And here is some more inspiration so you get a idea what I mean when I say "low-cost": and some more: http://www.viperpits.org/smf/index.php?topic=5895.0 Here is a instruction how to switch off the MFCD/Abris/Skval in the Hud-Only-view: Ka-50 ABRIS Edit ABRIS_init.lua in folder ScriptsAircraftsKa-50CockpitABRIS Line #11 ON Hud Only View: purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW}OFF: purposes = {render_purpose.GENERAL} Shkval Edit SHKVAL_init.lua in folder DCS Black Shark 2ScriptsAircraftsKa-50CockpitSHKVAL Line #13 ON in Hud Only View: purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW}OFF: purposes = {render_purpose.GENERAL} CautionLights Edit CautionLights_panel.lua in folder DCS Black Shark 2ScriptsAircraftsKa-50CockpitCaution_lights_indicator Line #2 ON Hud Only View: purposes = {render_purpose.HUD_ONLY_VIEW}OFF: purposes = --{render_purpose.HUD_ONLY_VIEW}A-10c MFCDs Edit MFCD_init.lua in folder ScriptsAircraftsA-10CCockpitMFCDindicator Line #16 ON in Hud Only View: purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW}OFF: purposes = {render_purpose.GENERAL}__________________________________________ Edit: This relates and will come handy if you want to build your own pit with a real HUD while keeping the overall render small : edit:

I hope everyone has a favorite http://www.tailormadedecals.com/index.php?option=com_docman&Itemid=34

Hi Sub17 majority rules F-16, dont worry the day the F-16 is retired is the day the global Air Force structure disintegrates.....LoL .............Its a REVIVAL CRUSADE OF F4........:smilewink: F4 The MOTHER OF ALL COMBAT SIMS ....... it keeps re-spawning and people wonder why........LOL

well I'm not that techy, so I'm afraid I can't help you with that. You may want to hit serif forums and pop a question though. they are quick to respond from my experience.

Try this: CockpitLocalPoint[su_25T] = {3.906, 0.466, 0.0}

Me too :) Its a true picture from the future...but even the future is subject to change :)

perfect work, THX:thumbup:

I just had a somewhat funny image pop into my head: Matt's house, with a bunch of simmers outside trying to get in, zombie-style :P Instead of braaaaiiiins, we go siiiiiiiiiiim..... Anyway! Carry on, nothing to see here! (are we there yet?)

Try copy F-15 Kabina.cmd from FC2 to dcs world... backup su-25t kabina.cmd in dcs world... delete orignal su-25t kabina.cmd in dcs world (dont delete the backup) rename F-15 Kabina.cmd to su-25t kabina.cmd run the game.. note u will still have su25t hud and f15 mfd will work for gorund targets

I think fighter ops never release..:D but don't worry because we have DCS :thumbup::thumbup:

nice work, thank you

This is awesome. You mentioned in another thread about the HUD being not correct in 3D projection. If we were to export the HUD this way then we can enjoy DCS in 3D and also have a working HUD right?

Great work on the HUD export!!! I think you can remove the first surface mirror and the lens if i recall correctly the guys at VP got it to work with just an LCD.

Not a bad guess, but also not necessarily correct. I believe that ED is not discounting the possibility of providing an AFM SDK. I would guess that the AFM is still a WIP (but then again, it may be a WIP forever - always getting better :) ) in the sense that it is probably not yet completely polished or documented and thus effectively not ready for 3rd party consumption. Just my humble opinion.

.... Ten years later.............

Hi this thread its gone off topic a bit but its basically an F-16 FM request discussion. If more than one variant can be made which wouldn't be that hard you have the base and calculations for one F-16 FM and adjust minor differences for others. I'm no coder or dev but once you establish a base it should be fairly smooth and easy to have some variants F-16AM, F-16C, F-16i, F-16CD, F-16CJ or another way to put it is a Block 15 then just a Block 50/52 as an example If F4 Devs can accomplish this certainly DCS can make the dream right, seriously these guys do it full-time and a bigger team than F4 teams. This would be the same for other A/C's like F-4, F-14, F-15, F-18..... SU's..... Migs..... and so on Well its just me thinking out loud anyway. I'm still hoping for the best............................:thumbup:

Loving your new sun flare mod, diveplane. ;) Click for full-res.

I'm home now. 1st go to this folder in your install Eagle Dynamics\DCS World\Mods\aircrafts\Su-25T\Input\ <--- copy the File called su-25T. paste it onto your desktop or any handy file you have. It wont be staying here. Rename the File F-15e. Now put this file into C:\Users\YOUR USER NAME\Saved Games\DCS\Config\Input. Now go to C:\Users\Krazy\Saved Games\DCS\Config\Input\F-15e and open the LUA file NAME.LUA In this file its going to say return _('SU-25t') Replace it with return _('F-15e') Now you need to copy this whole input file again. C:\Users\Krazy\Saved Games\DCS\Config\Input\F-15e Paste it into --->>>Eagle Dynamics\DCS World\Config\Input\Aircrafts Now when you open up DCS world. Go to your options. The F15e will appear. Insert your controls. ECT Now make a mission in the ME and set the F15 to client. You can fly all you want now. The sim also crashed on me when i pressed the 6,7 keys. This did not happen in 1.1.1.1. Just like in the A10c beta where the further along in beta the less other aircraft worked.

Not to mention better on the HDD space (although I still have 10 installs in my ED folder...yeah don't ask).