Mrwell, I think you’ll like EDTracker very much,
PS: hope yours arrives soon.
Reboot.
Mrwell, I think you’ll like EDTracker very much,
PS: hope yours arrives soon.
Reboot.
Negative, Reboot, they changed it no so long ago. Now it act like a standard head device too.
I’m waiting for my 9150 chip to test it. A friend of mine already did it and it works good with BMS.
I think it’s best to wait until you get your EDTracker then I can try to help you getting it working with BMS because you apparently don’t know how it’s supposed to work!
What I posted above was actually a quote from the EDTracker site.
PS: I’ve had my EDTracker (9150 chip) for over a month now and use Opentrack with BMS, actually it works impressively well.
The EDTracker, accelerometer/gyroscope/magnetometer
The EDTracker device only pretends to be a joystick, so any game that allows you to map an analogue joystick to a head-look feature should work.
If your game only supports protocols such as FSX, TrackIR or FreeTrack, you can use the 3rd party software “Opentrack” to take your joystick input from EDTracker and emulate those protocols.
Headtracker In Action video!
A link to Viperpits
http://www.viperpits.org/smf/index.php?topic=10001.msg138621#msg138621
Works fine here.
Are you using Open Track with your other sims and games? if not then it’s OpenTrack’s settings that’s at fault.
Hi Vaughan, I’ve just been experimenting with the size of MFD’s in BMS, and I think I’ve found something interesting,
If I set the left export MFD to exactly 225x225 pixels, then I get (over on the android) a perfect image, perfect lettering,
now If I use just one pixel more, or less “224x224” or “226x226” then the image get’s spoilt and the lettering is bleary,
if you have time then try this, the results are very impressive.
BTW, i’ve switched off “Double Resolution Cockpit Displays”
Thanks vaughan, but I was expecting the results to be the other way round, never mind.
at the moment my computer is dead and I only have the wife’s PC to play with, so I can’t do the tests myself.
Over at Viperpits Yoda, (GiGurra) has continued this topic over there, take a look.
http://www.viperpits.org/smf/index.php?topic=3376.msg104289#msg104289
Vaughan, or anyone else, could you make a small test for me!
Test 1: setup one MFD with a size of 256x256 pixels and then write down the FPS in instant action.
Test 2: do the same test again but with a setting like this, -256
the mfd will be completely off screen but Jshepaerds APP can still find it.
the test is to see if having MFD’s off screen has an influence on FPS,
this is for testing Falcon, not sheperds APP.
I also tried all of the center pedestal gauges and it was very slow and jerky, but the MFD’s are smooth as silk.
Any way to adjust the resolution of the MFD picture at the Android end?
what are you meaning by “resolution”, size or picture quality?
if its quality then try increasing the size of the gauges that falcon produces, but if you make them to large then things will start slowing down.
Vaughan, try switching off JPG (remove tick mark) and it will use PNG format, much smoother, better picture, (for me anyway).
From the server side where JPG is ticked on the right side lower the percentage. With 10% u get pixelated but good speed with 30% I believe it’s good. 100% doesn’t work for me…
If JPG is not checked, the drawing data of the MFD’s is sent in PNG format, this is what I use, much better.
Now the FPS Impact LOL is a killer…
Lightning found that by running in “window mode”, helped considerably with FPS, that is why BMS runs “window mode” whenever MFD extraction is activated.
the problem with starting extraction manually (by adding the line “set g_bUseExternalWindows 1”) is that it isn’t running “window mode” and your FPS will fall, the best way to use Jshepards APP is to activate BMS extraction and use BMS “window mode”.
Also the connection thing works like hell I was stopping it from server side and restarting it making jpg % changes and it was displaying just fine… So abuse it it takes it lol.
Yes, I have also noted how stable it is, once started it doesn’t like to stop, one problem I found, if I turn my tablet onto its side and the image turns around and runs off the edge of screen, then I lose connection.
What do you mean by go into my WiFi connection?
Sorry, I meant to say look at the android WiFi settings, if that is written as a normal IP number, then try and use that on the computer ?
On my tablet I can see the same IP, in the WiFi settings and in the MFD app.
PM Jshepard, he is a member of this forum.
https://www.benchmarksims.org/forum/member.php?980-JShepehrd
Bushmaster, go into your WiFi connection and look at the IP,
I have the same address there. ?
of course mine looks like this 192.168.0.100
My conclusion is that PS UDP is not Android 4 compatible, both my phone and tablet are running ICS.
Hi Bushmaster, I also think the problem is with android 4, this was posted on viperpits,
WEEBO
Does not work on Android 4?
Jshepard
Hi Weebo,
I don’t have Android 4 yet, but it should work. Try it and post your results.
Thanks.
Shep
setup example for the left MFD…… you don’t need Falcon running for this
it is only a test to confirm connection.
1: Copy Local IP Address from the computer to Server IP on the android.
2: Copy Local IP Address from the android to Client IP on the computer.
3: Copy Local Port from the android to Client Port on the computer.
4: Copy Server Port from the android to Local Port on the computer.
5: Check Left MFD on the android.
6: go into the settings on the android and activate Left MFD.
7: press “Start Server” on the computer.
8: press “Connect” on the android…… and you should get a image of your desk top.
……perilously close…knowledge…swap chains…computationally expensive…painful…poorly supported…zap bits…such logic…understanding…texture thing…performance…
So what your saying, its more advanced than just copying an image from A to B
Thanks Mark.
Well…… GiGurra, did you get all of that, if you quickly put together an extractor app then I will volunteer as your beta tester,
what do say to that.
Reboot.
Falcon MFD-Extractor read-me
http://dl.dropbox.com/u/5918219/Stephen/Falcon%20MFD%20Extractor%20v0.1.10.0%20User%20Manual.docx
http://dl.dropbox.com/u/5918219/Stephen/Falcon_MFD_Extractor_v0.2.0.2_User_Manual.doc
Edit: from Lightning……read-me v0.1.10.0
Enabling 3D Exporting in OpenFalcon
To use Falcon MFD Extractor in 3D Cockpit Mode with OpenFalcon, you need to configure OpenFalcon to export image data from the 3D cockpit to shared memory. This involves editing the FalconBMS.cfg file, located in your OpenFalcon installation folder.
Telling OpenFalcon to export images from the 3D cockpit
To enable 3D Cockpit image exporting from OpenFalcon, you will need to add the following line to the end of your FalconBMS.cfg file:set g_bExportRTTTextures 1
This will tell OpenFalcon to export certain pieces of the 3D cockpit’s sensor/instrument imagery, to a bitmap in shared memory, at the coordinates defined in the 3dckpit.dat file (see the section in this document, entitled Obtaining 3D Cockpit Image Source Coordinates from OpenFalcon’s 3D Cockpit Definition Files, for more details on the 3dckpit.dat file)
Telling OpenFalcon How Often to Update the Exported Image
OpenFalcon has another setting that you can add to your FalconBMS.cfg file, which determines how often OpenFalcon updates the shared memory image. This setting looks like this:set g_nRTTExportBatchSize 5
The g_nRTTExportBatchSize parameter works like this: Suppose we use the symbol n to refer to the value that you’ve assigned to this parameter. OpenFalcon then says, every (2^n) +1 frames – that is, every ((2 to the power of n) +1) frames – I’ll export a new image to shared memory. Let’s look at a couple possible values and their effects:
Parameter Value Effect
set g_nRTTExportBatchSize 1 Shared memory image gets updated every 3 frames
set g_nRTTExportBatchSize 2 Shared memory image gets updated every 5 frames
set g_nRTTExportBatchSize 3 Shared memory image gets updated every 9 frames
set g_nRTTExportBatchSize 4 Shared memory image gets updated every 17 frames
set g_nRTTExportBatchSize 5 Shared memory image gets updated every 33 frames
set g_nRTTExportBatchSize 6 Shared memory image gets updated every 65 frames
set g_nRTTExportBatchSize 7 Shared memory image gets updated every 129 frames
set g_nRTTExportBatchSize 8 Shared memory image gets updated every 257 frames
set g_nRTTExportBatchSize 9 Shared memory image gets updated every 513 frames
set g_nRTTExportBatchSize 15 Shared memory image gets updated every 32769 framesSince exporting these images to shared memory tends to have quite an impact on your in-simulation Frames-Per-Second display rate, OpenFalcon lets you, the user, decide how often you want these shared-memory images to be updated.
Setting the g_nRTTExportBatchSize parameter to low values (resulting in frequent refreshes of the shared memory bitmap) will have definite adverse effects on your in-game FPS rates in Falcon; setting the g_nRTTExportBatchSize parameter to higher values will result in slow output rates. That’s the tradeoff.
If you do not specify a value for this parameter, the default value is :
set g_nRTTExportBatchSize 9
PS: I’m not a programer, I’m just one of the Beta Testers that helped Lightning with MFD-Extractor.
Reboot.
Yes but I believe he actually doesn’t use shared memory. He relies on the built in extractor windows being up and running, and then he can use windows APIs to read the pixels of those windows.
I’m still lost
Jshepard’s program is copying images from the “shared memory area”, just like Lightning’s MFD-E. nether of these programs get’s its data from shared memory, because there isn’t any MFD data in shared memory.
He relies on the built in extractor windows being up and running,
Now you’ve lost me, what is this “built in extractor windows” .
I also tried size 600 600 32 but it made no difference
Be careful changing the rttTarget it is very sensitive about size.