MFD Exporter utility

Advanced search

Help us keep Viperpit alive !

[lightning]

The latest MFD Extractor version is always available at:
http://www.assembla.com/wiki/show/lightningstools#MFD_Extractor

When asking for help with MFD Extractor, please post the following *with every new question*
(or PM me this info, if privacy is a concern)

 -- Which MFD Extractor version are you running ?
      -- are you running MFDE in networked or standalone mode?
 -- What Falcon version are you flying (OF45, OF47, AF [specify patch #], FF5, FF5.3, etc.)?
 -- What isn't working for you now?  Be very specific.
   -- Has it ever worked for you before?
   -- When did it stopp working? (if it worked before)
 -- Screenshots, if applicable.

Also, please attach the following files to your post.
1.) attach the log.txt file from within your c:\Program Files\Falcon MFD Extractor folder [or from wherever you installed MFD Extractor to]
2.) run dxdiag and click the "Save All Information" button.  Attach the file that you've saved.
       To launch dxdiag, perform the following steps:
          - On XP or Vista: click Start, then Run, then type "dxdiag" in the box and click OK)
          -On Win7: click Start, then in the "Search programs and files" box at the bottom of the Start menu, type "dxdiag" and select "dxdiag.exe" from the list

Etiquette:
* Please do not ask for support for very old MFD Extractor versions.  However, if you are experiencing issues with a new version and need to revert to an earlier version, you may find all earlier versions here.
* When posting log files, please do NOT cut-and-paste.  Just *attach* the entire log files to your message, as *attachments*.  Or, you can PM me or email me the *entire* unmodified files.  
* Please do not post partial log files and please do not otherwise tamper with the log files in any way. I cannot help you if I cannot determine what has gone wrong.
* English, please; or if that is not possible, please post your questions in your original language, and let someone else translate for you.  Please do not use Google Translate, or Babelfish, or any other machine-translation tool -- I can do that myself, if need be.
* If I haven't responded to your question in a reasonable amount of time (1-3 days), please feel free to ask again.  I won't get mad at you.
* If you are making a request for a new feature, please do not mix this request in with your bug report.  Make a separate post.  

Beer donations (and other donations) are always welcome.  

[Reboot]

Is this not the holy grail.




Good work Lightning
________________________________


Reboot.

[Reboot]

Falcon MFD Extractor and FalconGauges at the same time on the same screen .   


Sorry Bad photo      

_____________

 Reboot

[Reboot]

Lightning want's to see some videos.

(This is my 1st vid)


__________

 Reboot

[Reboot]

 Hi Lightning.

 One more video
 



_________

 Reboot.

[troptrop]

hello Lightning

i try your latest version (v0.1.5.0)

you are a Champion Sir !

Fantastic !!! (i use Falcon AF... i have some small problems with OF... )



my options for your exellent MFDExtractor :



and my actual cockpit :




thanks a lot Lightning

Goupil

[Retro]

Just found another old post talking about that feature

This is in b4, but not really useable I am afraid. You can play around with this by setting this line

set g_bExportRTTTextures 1

Then you have to specify how often the texture is to be updated.. valid values are 1, 2, 4, 8, 16 (I think you get the idea) [i think this info was wrong in the post]. The RTT texture will be chopped up into n horizontal chunks (where n is the above number), read from video mem into system mem and made available to the reader application. And this vidmem->sysmem transfer is the bottleneck Sad

set g_nRTTExportBatchSize 2

In order to read the texture I've hacked a quick application together, just place it anywhere, and execute once f4 has started.. it will start updating once you enter the 3d pit. Note that this does not work across the network (obviously). Oh please note that it is meant to be used with a 512x256 texture [talking about my export tool here, not the rtt functionality itself] so all other texture sizes will be stretched.

One way to minimise the fps hit would be to decrease the size of the rtt texture (let's say to 512x256 or even 256x256), "real" pit builders do not need the rtt rwr and ded anyway, so they could be deleted from the rtt texture. Another way would be to increase the batch size, however that makes the display real laggy which is not desireable for most mfds.. not sure. A third way could be to split the one global rtt texture in the code into a few smaller ones, so that the user can decide which to export, and at what rates.. the ultimate solution of course would be for jam to whip up a new engine which supports output to several display adapters..

If you want to build your own reader app (but I doubt anyone would be crazy enough to do this [did not know about lightning back then]), the shared mem area is called "FalconTexturesSharedMemoryArea" and contains a DDS texture.. just read the DDS header, then you will get the size of the rest of the texture so you can acquire the needed memory and access the rest.

[Cannon]

Here is a small video I made ! 

http://www.youtube.com/watch?v=nJ98b9QBMoc

[thommo]

Short YouTube vid of 0.1.7.0 doing the 3D pit 16 bit at "5".

First part I'm running the MFDs on top of Falcon Gauges, then larger MFDs by themselves showing video in the MFD.

http://www.youtube.com/watch?v=vy-WxL01xDo

[Aeyes]

Some good news about the 3D cockpit 'shell'.
With some good help from Coolhand the LOD now functions ok, thanks CH !

Regarding FPS raise it is hard to tell since I havent compared them (didnt run the latest extractor yet), but what I do see is that the 3D shell with canopy and liftlines only, runs ultrasmooth in the normal setup.  If you dont want reflections and liftlines for SA guidance, disable in the UI.
You will only see the tail and wings with loadout.

I have also edited the 3dckpit.datfile to move the MFD/HUD/DED/RWR data to a place where you can not see it but it is present in the shell. The DED and RWR data can easily be removed by deleting the lines in the 3dckpit.datfile that tell where they are positioned.
Also, you can adjust yourself how far you will be able to look down in this line:
viewlimit_pitch_down 50.0;

The 3D cockpit 'shell' .LOD and 3dckpit.dat files are attached.
To install the .LOD you need to use LE until a F4patch file or similar is made.
Backup Koreaobj.HDR, run LE, Open normal/parent #1, and open (1)LOD#0.
Go to 'Action/replace model and select the new .LOD

For the 3dckpit.dat, go to art/ckptart and back up the default 3dckpit.dat and replace.
Run Falcon and check the emptyness and environment  with the tool and report your findings please.

Next is 2D but that is a different story.

[thommo]

Also, any pics or vids of the newest pit?

Aeyes, your 3D pit works well thank you:




YouTube clip:
http://www.youtube.com/watch?v=TSERF7gZsqc
(it is a little jerky due to Fraps capturing)

Aeyes, on your flashing, when going back to OF from the desktop (I only do this from the menu screens eg open TE screen first), try mouse clicking on it's minimised button on the Taskbar instead of using the ALT TAB.

Don't take MFD Extractor's CPU util too seriously

Yeah, there was plenty of available CPU according to that capture.  No problem.

[AiRdAncE]

The low framerate is caused by a worthless computer (Pentium D 3.40Ghz with 1GB RAM and NVidia GeForce 7100GS)... need an upgrade bad

 

[Aeyes]

A new 2D/3D cockpit shell version is available ! Took me a bit longer as expected and some sweat and tears but it is better
 
From the readme:

Description:
Homepitbuilders Viperpit, emptied 2D and 3D cockpit shell for OF F-16blk52, v1.3   02-mar-2008
To be used with Lightning's MFD/HUD extractor tool, see the Viperpits.org forum


This mod has:
-  a 2D views shell 1600x1200 res with HUD and MFD data at the bottom.
- a 3D shell with canopy and liftlines and tails/wings only.


*****The 3D cockpit shell*****
If you dont want reflections and liftlines for SA guidance, disable them in the UI.
You can adjust yourself how far you will be able to look down in the cockpit by adjusting this line in the 3dckpit.datfile: viewlimit_pitch_down 0.0;
The higher the number the more downwards you can see.
A range from 0.0 - 50 is safe and tested

The 3dckpit.datfile serves to move the MFD/DED/RWR data to a place where you can not see it but it is present in the shell.
The DED and RWR data can easily be added/removed by adding/deleting the lines in the 3dckpit.datfile that tell where they are positioned. 
The HUD can be removed by renaming the noHUD3dckpit.dat to 3dckpit.dat adding the original 3dckpit datfile HUD positioning data again, only the # 0 is changed in there.



*****The 2D cockpit shell*****
There are 2 modes, switchable with Shift-2,
One mode is for 4:3 screen users, resolutions like 1600x1200, 1280x968, 1024x768
The second mode is for widescreen monitor users, like 1440x900,1680x1050, 1920x1200

The source coordinates in the MFD extractor show the pixels on the screen in X/Y coordinates:
LEFT  RIGHT
TOP BOTTOM
So changing these coordinates should be done by adding/deducting for the right direction.

The following are the 2D cockpit shell source coordinates for the HUD and left and right MFD's to enter in the MFD extractor options menu at the source coordinates:
1600x1200 resolution:
HUD:
Upper left X: 620    Lower right X: 980
Upper left Y: 555    Lower right Y: 915

LEFT MFD:
Upper left X: 599    Lower right X: 799
Upper left Y: 999    Lower right Y: 1199

RIGHT MFD:
Upper left X: 800    Lower right X: 999
Upper left Y: 1000    Lower right Y: 1199


1024x768 resolution:
HUD:
Upper left X: unknown yet    Lower right X: unknown yet
Upper left Y: unknown yet    Lower right Y: unknown yet

LEFT:
Upper left X: 383    Lower right X: 511
Upper left Y: 639   Lower right Y: 767

RIGHT:
Upper left X: 512    Lower right X: 639
Upper left Y: 640    Lower right Y: 767



1680x1050 resolution (use shift-2) These coords are tested on a 1920x1200 monitor so could be off a bit.
HUD:
Upper left X: 620    Lower right X: 980
Upper left Y: 555    Lower right Y: 915

LEFT MFD:
Upper left X: 599    Lower right X: 799
Upper left Y: 999    Lower right Y: 1199

RIGHT MFD:
Upper left X: 800    Lower right X: 999
Upper left Y: 1000    Lower right Y: 1199


1920x1200 resolution (use shift-2) If someone checked these let me know please.
HUD:
Upper left X: unknown yet     Lower right X: unknown yet
Upper left Y: unknown yet     Lower right Y: unknown yet

LEFT MFD:
Upper left X: unknown yet     Lower right X: unknown yet
Upper left Y: unknown yet     Lower right Y: unknown yet

RIGHT MFD:
Upper left X: unknown yet   Lower right X: unknown yet
Upper left Y: unknown yet   Lower right Y: unknown yet




Installation:
To install the .LOD (model)  you need to use LodEditor 610 or higher until a F4patch file or similar is made as installer.
See Freefalcon.com forum for Lodeditor
Backup Koreaobj.HDR, run LE, manually enter the # 1 at 'Normal'1, and click on 1  to open LOD#0.
Go to 'Action/replace model and select the new .LOD

For the 2D cockpit shell, go to Falcon4/art/ckptart and back up the 'ckptart' dir and replace with 'ckptart' dir of this zip.
Although it has been tested and showed no harmfull results use and run at your own risk, back up what you change first !




Changes v1.3
- 2D and 3D HUD are aligned and same size and height
- Added all views to the 2D cockpit so you can pan around
- Added MFD's to all views
- Added widescreen support to be enabled with Shift-2
- All F-16's are now 2D/3D cockpit shells

Changes v1.2
- Added 1024x768 resolution coordinates in the readme
- Changed the size of the black MFD backgrounds fields so that 1024res users have more space

Changes v1.1
- Changed the readme and instructions to be more precise
- Changed the 3dckpit.dat to have a HUD at 12 o'clock
- Added a noHUD3dckpit.dat file in case the HUD needs to be gone.
- Changed the pitch down number in the 3D shell to 0.0, limiting downward views


Aeyes


http://www.cockpits.net/files/freeware/VIPERPIT_2D_3D_Shell_v1.3.zip 3.3 Mb

[lotzo]

all 3 videos has the same  f4 settings

Instant Action
Batch size 2

one MFD on the same pc ->www.diehappyonline.de/1.avi
cursor move->www.diehappyonline.de/3.avi
one MFD over the network->www.diehappyonline.de/2.avi over network it´s not smooth

mfg
Lotzo

[lotzo]

hello
now i can export 256pix MFD without problems  with
rttTarget 256 768 16; batch size2


mfdleft  0  -7.620  11.240    0  -4.220  11.240    0  -7.620  14.540   0 256 256 512 c;
mfdright 0   4.260  11.240    0   7.660  11.240    0   4.260  14.540    0 512 256 768 c;


www.diehappyonline.de/5.avi

www.diehappyonline.de/4.avi

lightning thanks for your work

lotzo

19:44 UTC
September 03,2010

Bones308th (41)

Ka-Bar03 (5074)
AiRdAncE (3955)
Crease-Guard (2725)
Nigel (2387)
Red Dog (2330)
Kneeling Warrior (2326)
Nikolas_A (2148)
lightning (2126)
101-Douxx (2024)
Flareless (1708)