Beta Release: GPT (cockpit texture extraction, remote cockpit control, shm mirror)
-
Ok. Command line parameters added to the todo list. I should be able to get them working with gpt.
Yes you can run the displaysreceiver on the same machine as the game.Can you give me an example of command line parameters that BMS supports, so I can test that my fix works?
The ones that I know are -window and -ef.
With -ef you can enable “Eye Fly”, which is a free cam that will let you move inside Falcon 3D. But you need to configure a key for that before. In defaults key mapping, I reckon is Ctrl + i
Thanks for your support.
-
The ones that I know are -window and -ef.
With -ef you can enable “Eye Fly”, which is a free cam that will let you move inside Falcon 3D. But you need to configure a key for that before. In defaults key mapping, I reckon is Ctrl + i
Thanks for your support.
Thanks, verified now that I got it working on the next version.
Also 80% certain I got xp support covered.Maybe I should announce the release in a new thread? And we could close this old one?
-
thanks for coming around again GiGurra!
my setup (as it was - no time now) : touchscreen on a slave PC with helios with modified (complete new keyfile) roguesqdn profile + +.
It is over a year now that I tried all that. Have not been airborne since. (so i might write BS)
Could you tell why mfde had better performance on many small gauges while your suite blew mfde away on the mfds and some of the big ones (IIRC Velocity and Altimeter) ?
You used the inbuild BMS extraction tool, right?
If you would provide the .sln for VS and take the time to make the most important annotations I would be a very happy man, I swear! : )
thank you for sharing your solutions!
+1 here for a new thread.
-
Thanks, verified now that I got it working on the next version.
Also 80% certain I got xp support covered.Maybe I should announce the release in a new thread? And we could close this old one?
Thanks for understanding about XP. Already had to delete DCS from my system since their latest update is not supporting XP. Liked to fly the UH-1.
Not sure about new threat, hardcore users will find find exiting threat anyway. But for new users it perhaps is good idea to start new threat when you launch “new style GPT”
-
thanks for coming around again GiGurra!
my setup (as it was - no time now) : touchscreen on a slave PC with helios with modified (complete new keyfile) roguesqdn profile + +.
It is over a year now that I tried all that. Have not been airborne since. (so i might write BS)
Could you tell why mfde had better performance on many small gauges while your suite blew mfde away on the mfds and some of the big ones (IIRC Velocity and Altimeter) ?
You used the inbuild BMS extraction tool, right?
If you would provide the .sln for VS and take the time to make the most important annotations I would be a very happy man, I swear! : )
thank you for sharing your solutions!
+1 here for a new thread.
Not quite sure here what you mean about mfde and performance. GPT doesn’t do gauges, so how do you compare performance of vvi and altimeter?
I have not used the built in tool when developing GPT - instead GPT hooks on to the Direct3d engine of BMS to download the required textures directly.
The C++ parts of GPT (only the displaysTransmitter is in C++) is already building with Visual studio (2013). A sln file is generated with CMake through the python build scripts. All can be downloaded from github: https://github.com/GiGurra/gpt .
For transmitting MFDs I use a library called Libjpeg-turbo which is basically a very fast jpeg image compressor. Every frame recorded from the game’s direct3d engine is compressed to a jpeg image and sent to the slave pc. Normally you use video streams for this purpose, but the gpt solution is better for low latency purposes. However GPT requries about 10x (!!!) the bandwidth, so it’s not useful for internet streaming (the stream is about 40 mbit/s).
-
thanks, yes the comparison must have been between mfde gauges and the helios ones. helios small gauges where slower (slave pc: intel 6750 core 2 duo )
special thanks again because without your collection of tools i had to make the mfds very slow and small (using mfde).
not of your concern - but as a sidenote for thread readers:
for touchscreen users a second pc is a must because touching the screen is always recognised as a mouse click by
BMS on the main machine (bms uses a relative mouse coursor - which works even on a second monitor) and might flip a switch in the 3D pit while trying to flip
a switch on the 2D helios panel. this was discussed in the touchscreen section and dunc took a note of the issue.your tools made the helios setup on a slave pc very easy.
-
thanks, yes the comparison must have been between mfde gauges and the helios ones. helios small gauges where slower (slave pc: intel 6750 core 2 duo )
special thanks again because without your collection of tools i had to make the mfds very slow and small (using mfde).
not of your concern - but as a sidenote for thread readers:
for touchscreen users a second pc is a must because touching the screen is always recognised as a mouse click by
BMS on the main machine (bms uses a relative mouse coursor - which works even on a second monitor) and might flip a switch in the 3D pit while trying to flip
a switch on the 2D helios panel. this was discussed in the touchscreen section and dunc took a note of the issue.your tools made the helios setup on a slave pc very easy.
I also noticed that Helios has a bit slow update rates. I mirror shared memories with flight data at 50 Hz (changable in the config file), but Helios rendering seems locked at 25ish.
-
OK. Heads up. New release is out. Check the first post of this thread if you’re interested.
-
Hello GiGurra
i installed v2 and tested it
i have it working but i have a 3 sec delay in the mfds from one pc to another(network) i also posted a topic on your websiteany ideas
greets Scratch
Solution
After talking to GiGurra who told me to reduce the fps in the display-reciever config file …… it works (FPS 30)
Thanks GiGurra
-
Intalled v2 after vacations and it runs great.
What are the advantages of this version over the previous one?
Thanks again.
-
Intalled v2 after vacations and it runs great.
What are the advantages of this version over the previous one?
Thanks again.
The main differences are quite small for the end user:
- GPT now has a proper build script and source code is available at https://github.com/GiGurra/gpt
- GPT now uses MGen and MNet (the new data modeling toolkit I’ve been working on)
- GPT now uses JSON for config files, instead of previous unflexible ini files (example: https://github.com/GiGurra/gpt/blob/master/gpt-displaystransmitter/gpt_displaystransmitter_cfg.json)
- GPT DisplaysReceiver: now starts with black screens
- GPT DisplaysTransnitter: now only streams over tcp (BMS handles sharedmemory case natively)
- GPT DisplaysTransmitter: can now stream to multiple network targets
- GPT DIsplaysTransmitter: Now supports passing command line parameters to the game itself
-
The main differences are quite small for the end user:
- GPT now has a proper build script and source code is available at https://github.com/GiGurra/gpt
- GPT now uses MGen and MNet (the new data modeling toolkit I’ve been working on)
- GPT now uses JSON for config files, instead of previous unflexible ini files (example: https://github.com/GiGurra/gpt/blob/master/gpt-displaystransmitter/gpt_displaystransmitter_cfg.json)
- GPT DisplaysReceiver: now starts with black screens
- GPT DisplaysTransnitter: now only streams over tcp (BMS handles sharedmemory case natively)
- GPT DisplaysTransmitter: can now stream to multiple network targets
- GPT DIsplaysTransmitter: Now supports passing command line parameters to the game itself
Should we notice any performance gain?
-
Should we notice any performance gain?
No - if anything the generalizations I have made may give you a small performance loss. The cost of having maintainable code I guess.
-
Ok, thanks again yoga for the epic software update.
throwing this one out too the others.
my setup is
gaming PC one screen, 920 i7 4.2ghz 12gb ram 660ti
server PC with touch screen two 2.66 ghz quad core 24gb ram with 6650 ati running Helios and saitek switch panel.After support from yoda we have managed to setup both pc’s to run the successful extraction of mfd’s, dead, rwr…
I have installed Helios onto my server PC and made sure the correct key file is being used.
when typing on the keyboard on the slave PC it sends the key presses over to the master PC. However I have not been able to get any output from Helios switches, so when flicking a switch nothing is happening. When I open word doc on slave PC it does however transmit as a key output, so I know it’s working just not sending to master PC.
i am at a loss to why this could be happening. Maybe I missed something, seems a shame as I am getting 85-90 fps with all the mfd’s rwr and ded extracted using a single screen on the gaming PC.
thanks again for any advise…
-
Hi,
Had something similar before.
That time it was caused by an automatic IP change. Best to check your machine IP with IPCONFIG and then look for your GPT IP settings.Hope it will solve for you also.
-
OK. Heads up. New release is out. Check the first post of this thread if you’re interested.
Thank you GiGurra, very great work.
I am impatient to see the V0.3
-
Hi Sparks, had a good day today changing my IP settings in the cfg files, removed firewalls, no luck…. Still no helios output really frustrated as everything else is work sweet… my server is up too 50% usage and the frame rates gone from 32 to 90/100 Just need to figure out why helios outputs are not taking on the master PC … Thanks again for your advice…
-
OK, well I just got it to work, no lag nothing!!! very happy… All I needed to do was to run Helios in administrator mode!! Cannot believe I did not try that first time. Just wanna thank Yoda aka Gigurra Your are the man!!
-
One last question I have is how on earth do I now get lights to update on the slave helios?? is this done by arranging an extra interface?? through helios
-
Thank you GiGurra, very great work.
I am impatient to see the V0.3
Cool. Well I haven’t had any real bug reports so far and I’m not sure what to put in a v0.3 version. (The only issue so far was to perhaps add support for automatic framerate throttling if the network layer or slave pc cannot keep up with the master pc)
What kind of features would you like to see for 0.3?