Beta Release: GPT (cockpit texture extraction, remote cockpit control, shm mirror)
-
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% ^^).
-
hello GiGurra
Thanks for your works
I had build a specific post in French C6 forum
http://www.checksix-forums.com/viewtopic.php?f=286&t=185523&start=75#p1512317I had make a specific build v0.31 with in “components” 3 parts :'GPT_Transmitter", “GPT_Receiver_F-16” & “GPT_Receiver_M2K”.
The “GPT_Receiver_M2K” had the *.json" with specific x and y for Mirage2000. It is for dummies…I hope you are ok with that…
Thanks
Sharknoir -
GiGurra,
Thanks so much for these tools! I used the previous version on 4.32 and it was perfect.
In the new version I’m getting a bit of lag between my actions in the sim, and what I see on the receiver displays. Could changing the JPEG quality help minimize this? Does it affect the delay? Going from 50hz to 30hz definitely helped, but I’m thinking if I go lower than 30hz, there might be less for the receiver to deal with, but it won’t be smooth.
-
Hello,
The new version 0.3.1 only work if i have bms with Cockpit Displays to External Windows. This is correct?
I have a gpt old version that work with bms 4.33 x86 in full screen that have better fps…
-
Hello,
The new version 0.3.1 only work if i have bms with Cockpit Displays to External Windows. This is correct?
Not correct. See the readme. You need to enable two settings in a bms config file.
do NOT enable “Cockpit Displays to External Windows”GPT now runs entirely outside bms, and if you have at least a 4 core CPU should not affect BMS fps at all.
What affects bms fps slightly (exactly same as old gpt) is download of the cockpit textures to ram. -
GiGurra, can you please comment why is this version of displays extraction stops extracting after alt+tab. Previous version was working fine after switching back and forth.
-
GiGurra, can you please comment why is this version of displays extraction stops extracting after alt+tab. Previous version was working fine after switching back and forth.
Because of a bug in BMS. Confirmed by devs in this thread:
https://www.benchmarksims.org/forum/showthread.php?23390-Bug-Report-FalconTexturesSharedMemoryArea-stops-updating-after-ctrl-alt-delThey said it will be fixed in their next patch.
In short: The old GPT used a hack to get display data from BMS - which doesn’t work with 64bit. The new GPT uses proper display data extraction from BMS - but that proper method has a bug which can be seen if you minimize bms (like alt-tab or ctrl-alt-del).
As soon as the BMS devs patch BMS -> GPT will work with alttab etc.
-
Hello,
All work fine until i plug 2 usb samsumg u70 on my pc, the Displays Transmitter still waiting for bms, no found that was started.
with the 2 Samsung u70 pluged only work if i have enable “Cockpit Displays to External Windows”.Tx
-
Hello,
All work fine until i plug 2 usb samsumg u70 on my pc, the Displays Transmitter still waiting for bms, no found that was started.
with the 2 Samsung u70 pluged only work if i have enable “Cockpit Displays to External Windows”.Tx
Sorry no clue what could be the problem. Unless you accidentally removed the export configuration from bms.cfg.
Do you have some buddies to help you with configuring GPT?GPT should NOT in any way require “Cockpit Displays to External Windows”.
-
All works fine without the u70.
With the u70 “Displays Transmitter” not found that falcon bms is running.
With old gpt version i don’t have problems with the u70.
-
Just to confirm, I use GPT with 2 small side monitors for MFD powered by 2 vid cards on the same PC and do not enable the BMS “Cockpit Displays….” Must be something with your individual setup. Win 7-64, NVidia GTX 760, BMS 4.33. Very difficult to assist remotely, though, beyond the obvious. I start the Displays Transmitter, then Displays Receiver, then BMS.