Beta Release: GPT (cockpit texture extraction, remote cockpit control, shm mirror)
-
Hi all! What instruments it extracts? Looking into “displayreciever-cfg.json” i only read for MFDs, DED, HUD and RWR.
Does anyone know if it extracts others instruments licke MfdE?If you want to giva a try I have developed a new extractor (using ideas from gigurra and others) that allows you to export all the instruments you want.
You can find it here
https://www.benchmarksims.org/forum/showthread.php?22901-YAME-Suite-v0-2
-
Hi all! What instruments it extracts? Looking into “displayreciever-cfg.json” i only read for MFDs, DED, HUD and RWR.
Does anyone know if it extracts others instruments licke MfdE?Only LEFT/RIGHT MFD, RWR, DED and HUD.
But it also mirrors the shared memory block over the network so you can run any of your favorable instrument display utility on the networked PC (I use Helios).
MFDE doesnt extract instruments (like puctures). It reads flight parameters from BMS shared memory and visualize the instruments by itself just using the extracted parameters. -
If you want to giva a try I have developed a new extractor (using ideas from gigurra and others) that allows you to export all the instruments you want.
You can find it here
https://www.benchmarksims.org/forum/showthread.php?22901-YAME-Suite-v0-2
How it works? Only in network mode or also standalone? Is there a guide? Thank you
-
If you want to giva a try I have developed a new extractor (using ideas from gigurra and others) that allows you to export all the instruments you want.
You can find it here
https://www.benchmarksims.org/forum/showthread.php?22901-YAME-Suite-v0-2
First of all, thanks for developing a new tool.
That been said, I wold like to play devil’s advice here and ask you:
What are the advantages of your tool over GPT?
Is its performance hit less than that of GPT?Thank you
-
First of all, thanks for developing a new tool.
That been said, I wold like to play devil’s advice here and ask you:
What are the advantages of your tool over GPT?
Is its performance hit less than that of GPT?Thank you
I have not made any comparison. Mine is pure C++, no java interface, so is a bit easier to make it run. The only different thing is that you can have choose to have only MFD extraction and/or others cockpit instruments on the client machine. All displays can be on different windows each activable via a key press. So you can have all the engine instruments in a window, keep it hidden and with the press of a key you can make it show; when checked hit the key again and the window will be hidden again. Plus you can use the “panel” application that runs a web server on the server pc that allows you to interact with Falcon BMS via simples web pages that you can display on every device you have that supports HTML.
-
I have not made any comparison. Mine is pure C++, no java interface, so is a bit easier to make it run. The only different thing is that you can have choose to have only MFD extraction and/or others cockpit instruments on the client machine. All displays can be on different windows each activable via a key press. So you can have all the engine instruments in a window, keep it hidden and with the press of a key you can make it show; when checked hit the key again and the window will be hidden again. Plus you can use the “panel” application that runs a web server on the server pc that allows you to interact with Falcon BMS via simples web pages that you can display on every device you have that supports HTML.
Thanks for the tool. I will give it a try.
-
Hello GiGurra,
Is it possible in a new version to add MFD extraction works with all cockpits in Falcon4? (Actually not works with Mirage2000 cockpit…).
Thanks for your job
Sharknoir -
Ive had some PMs with questions if there will be a new GPT release to support 64bit 4.33.
Answer - yes. There will be a new GPT version on eventually (based on FalconTexturesSharedMemoryArea).In short it will be like a small daemon app you run on the game pc instead of a d3d hooked game exe. Not sure how soon I will have the new version out.
-
Fantastic news…
The 4.33 support F-18 cockpit and Mirage2000 cockpit etc… If the new GPT x64 can export MFD, many many men will love you… And with an easy install and configuration, you are our GOD for pitbuilders… lol
I don’t know if it is a good idea, but the same install and configuration than the very old F4Glass???
http://www.checksix-fr.com/bibliotheque/index.php?Fichier=5829Thanks for your time GiGurra…
-
Great news GiGurra!
Any chance you just recompile the old build for x64 before making a new daemon type App? So we could start flying 4.33 with our pits right away? -
Great news GiGurra!
Any chance you just recompile the old build for x64 before making a new daemon type App? So we could start flying 4.33 with our pits right away?+1
-
The OLD GPT works with the 4.33 x86 version (Ok i prefer the x64 more stable).
But with the old who working with 4.33 x86, i can wait the best GPT x64… -
Great news GiGurra!
Any chance you just recompile the old build for x64 before making a new daemon type App? So we could start flying 4.33 with our pits right away?Sry I wish it was that simple :(.
GPT 0.2 relied on Microsoft Detours library which is 32bit only unless you pay $10.000 (I’m not joking).
So I’d need to swap that out for something elseAlso it relied on a 32bit library called turbojpeg (although that is probably available in 64bit as well)
Anyway. I have had good success reading data from Falcon shared texture memory instead with good performance, so the new gpt version should be out tomrrow the latest, and contain no d3d hooks.
-
Sry I wish it was that simple :(.
GPT 0.2 relied on Microsoft Detours library which is 32bit only unless you pay $10.000 [emoji14] (I’m not joking).
So I’d need to swap that out for something elseAlso it relied on a 32bit library called turbojpeg (although that is probably available in 64bit as well)
Anyway. I have had good success reading data from Falcon shared texture memory instead with good performance, so the new gpt version should be out tomrrow the latest, and contain no d3d hooks.
You are the man!
ThanksProblem is that online you can’t mix versions.
I tried yesterday to connect with somebody who was running the 64 instead the x86 and we got a mismatch error.
And I assume most guys would prefer to use the x64.
-
I just did the first proof-of-concept tests with shared memory as a source for texture data. it works perfectly. So now I just need to implement all this stuff less hackish.
Oh for those of you that wonder this will also work for other aircraft like the Mirage (I just tested).
This means you can run either x64 or x86 gpt wont care. It will run outside bms. Performance is about the same as old GPT.
-
Version 0.3.0 (super-beta^^) available for experimentation with 4.33 here:
https://github.com/GiGurra/gpt/releases/tag/v0.3.0I have to run but will be back and try it more later during the weekend
-
Fantastic work GiGurra! You are the man!!!
-
ont care. It will run outside bms. Performance is about the same as old GPT.
After some testing I have found a problem. Displays are lagging the second machine. New display transmitter doesnt react on MaxFPS setting in the configuration file. Therefore the flow of 50 pfs is too high for my setup.
-
Hello,
GiGurra had found this bug yesterday…
There is a new Beta version the 0.31
-
After some testing I have found a problem. Displays are lagging the second machine. New display transmitter doesnt react on MaxFPS setting in the configuration file. Therefore the flow of 50 pfs is too high for my setup.
Yep. Known. This (the fps limiter) is fixed in 0.3.1. just replace the transmitter jar with the 0.3.1 release
0.3.0 was actually “unlimited”, which meant like 200 fps and 200 mbit (and of course one cpu core @100% ^^).