Jump to content

MFCD for Android tablets (phones)


colo

Recommended Posts

the TM MFCDs dont provide an alternate screen picture though, they are just the buttons.

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
Share on other sites

  • Replies 608
  • Created
  • Last Reply

Top Posters In This Topic

the TM MFCDs dont provide an alternate screen picture though, they are just the buttons.

 

But I can put small 2 LCD monitors behind it right ?

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

Link to comment
Share on other sites

yup, or glue them to a tablet or something :)

 

See Here for a "Guide":

http://forums.eagle.ru/showthread.php?t=93389

 

 

 


Edited by SkateZilla

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
Share on other sites

It is totally easy to put an mfd screen on an tablet by the way.

Just download I display an transfer the MFD to the display....

 

The trick are the buttons. I asked ED to bring an update to allow snapview porting to external screens, but that's not working.

 

Anyhow, if we can have an app for that, that's maybe even better....

Link to comment
Share on other sites

Absolutely love this!

 

:thumbup:

Gigabyte GA-Z87-UD3H | i7 4470k @ 4.5 GHz | 16 GB DDR3 @ 2.133 Ghz | GTX 1080 | LG 55" @ 4K | Cougar 1000 W | Creative X-Fi Ti | TIR5 | CH HOTAS (with BU0836X-12 Bit) + Crosswind Pedals | Win10 64 HP | X-Keys Pro 20 & Pro 54 | 2x TM MFD

Link to comment
Share on other sites

It should be able to use "Helios"-gauges/switches on Android...

;-) So everybody can compose his own needs...

 

By the way: Does it work via WLAN or USB-Cable?

 

Helios is great profi software, curently I am not able to implement it.

Implementing and increasing details for MFCD and CDU will be enough for me for several months.

 

It works via WLAN - it connects to PC ip address.

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

Link to comment
Share on other sites

OK, I did as described:

Basic F-15C TEWS display that connected via export.lua to DCS World/FC3.

I did all your stuff completely, but it doesn´t work here.

 

Initial beta

Please use following exportTWS.lua file for export from DCS:

https://docs.google.com/file/d/0B7tSPZhl7CP2NGRDcGxqeEc2Z1E/edit?usp=sharing CHECK

Instructions:

1. Create directory $HOME\Saved Games\DCS\Scripts\ CHECK

2. Copy export.lua from C:\Program Files\Eagle Dynamics\DCS World\Scripts to $HOME\Saved Games\DCS\Scripts\ CHECK

3. Copy the above telemetryTWS.lua file into $HOME\Saved Games\DCS\Scripts\ directory. CHECK

4. Add the following line at the end in export.lua to:

dofile( "C:\\Users\\[username]\\Saved Games\\DCS\\Scripts\\telemetryTWS.lua ") LOOK AT QUESTIONS BELOW

5. Change [username] to your user name CHECK

6. Edit telemetryTWS.lua and change IP to Android table IP. You can check it in the android setting view for WiFi connection CHECK

7. Start the application on the device CHECK

 

Please note that it is very early beta, any feedback is welcome

So I did all the CHECK-marked stuff, but please take a look this:

- Is all bold marked stuff correct?

- I´ve downloaded an "ExportTWS.lua", not "telemetryTWS.lua"

- Do I have to rename the "exportTWS.lua" to "telemetryTWS.lua" (or rename inside a .lua-File?)

- Are the double-slashes // correct?

- What about the red brackets [] ..? Do I have to delete them?

 

Maybe you could help me, i´ll try run it on a Samsung Galaxy S2

(if it works there)

Greetz Purzel

 

PS: Seems to be a little complicated, if you have dynamic IPs in your WLAN.

But I hope, you´ll get a good working MFCD-App (with the "TM Cougar MFCD-switches" simulated on touchscreen!)


Edited by Purzel
Link to comment
Share on other sites

OK, I did as described:

Basic F-15C TEWS display that connected via export.lua to DCS World/FC3.

I did all your stuff completely, but it doesn´t work here.

Currently I am exporting only sensors from A-10C there are diffrent paths, I don't try exporting FC3 sensors yet.

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

Link to comment
Share on other sites

PS: Seems to be a little complicated, if you have dynamic IPs in your WLAN.

But I hope, you´ll get a good working MFCD-App (with the "TM Cougar MFCD-switches" simulated on touchscreen!)

 

I can add to menu connection via hostname also if it helps.

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

Link to comment
Share on other sites

I have made skeleton for CDU.

It works, but have ugly buttons and big lag.

 

The question is if I can use button bitmaps from game or should I ask Flying legends (as copyright holder for DCS) for permission.

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

Link to comment
Share on other sites

I can add to menu connection via hostname also if it helps.

That would be sooo great...

And sorry, I understood it as if you had that TEWS build for FC3 (F15C)

So if I understand that in the right way, that app is for A-10C...?

But what about the bold marked double-slashes, etc...? Is that correct?

 

Can I use button bitmaps from game or should I ask Flying legends?

Why not asking for permission, asking does not cost anything... if you get no permission use your own bitmaps (just change the colors slightly... or something like that)

 

I appreciate your work - keep on going! :thumbup::clap_2:

Link to comment
Share on other sites

That would be sooo great...

And sorry, I understood it as if you had that TEWS build for FC3 (F15C)

So if I understand that in the right way, that app is for A-10C...?

 

Currently yes it is for A-10C only, if I have it debugged and polished for A-10 maybe I will add another aircrafts.

 

Sorry I am using different way for exporting instrruments for A-10, it is simple

cause every instrument has its init scripts in

C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts

but for FC3 there is no such directory and from what I see from your snippet you are using different way so I don't know answer.

Intel Core i7 11700, 32 GB RAM, Nvidia RTX 4090, NVMe 3 TB, VR HP Reverb G2, Thrustmaster Warthog + pedals, Cougar MFDs, TrackIR, aInstruments

Link to comment
Share on other sites

OK, I did as described:

Basic F-15C TEWS display that connected via export.lua to DCS World/FC3.

I did all your stuff completely, but it doesn´t work here.

 

So I did all the CHECK-marked stuff, but please take a look this:

- Is all bold marked stuff correct?

- I´ve downloaded an "ExportTWS.lua", not "telemetryTWS.lua"

- Do I have to rename the "exportTWS.lua" to "telemetryTWS.lua" (or rename inside a .lua-File?)

- Are the double-slashes // correct?

- What about the red brackets [] ..? Do I have to delete them?

 

Maybe you could help me, i´ll try run it on a Samsung Galaxy S2

(if it works there)

Greetz Purzel

 

PS: Seems to be a little complicated, if you have dynamic IPs in your WLAN.

But I hope, you´ll get a good working MFCD-App (with the "TM Cougar MFCD-switches" simulated on touchscreen!)

 

Sorry, my mistake. It should be exportTWS.lua. I have fixed instructions in Play Store.

You should replace [username] including brackets with your windows user name

 

Leon

Link to comment
Share on other sites

Another great thing to probably implement down the line would be something like the set that LeAVu2 had (search by user "Yoda"). It had great extended MFD functionality for some of the FC3 aircraft (F-15C in specific).

If you aim for the sky, you will never hit the ground.

Link to comment
Share on other sites

Mmm that CDU looks great! :D

i7 7700K | 32GB RAM | GTX 1080Ti | Rift CV1 | TM Warthog | Win 10

 

"There will always be people with a false sense of entitlement.

You can want it, you can ask for it, but you don't automatically deserve it. "

Link to comment
Share on other sites

Please load that CDU to Google PlayStore... can´t wait for it - and not only me I guess.. ;)

 

Sorry I´m to stupid to understand scripting...

(from your PlayStore description)

 

1. Create directory $HOME\Saved Games\DCS\Scripts\ <- What means $HOME? Where exactly do I have to create this folder?

 

3. Copy the above telemetryTWS.lua file into $HOME\Saved Games\DCS\Scripts\ directory. <- Needs to renamed to exportTWS.lua, right?

 

4. Add the following line at the end in export.lua:

dofile( "C:\\Users\\[username]\\Saved Games\\DCS\\Scripts\\telemetryTWS.lua ") <- Are the double slashes // correct in a path?

You mean Add the following line at the end in exportTWS.lua, right?

For your understanding:

I have DCS:World installed at F:/program files/Eagle Dynamics/DCS:World.

In C:/User/my computer-username/saved games/dcs/ is the other path where my sreenshots/missions/tracks/scripts/etc are. Is that the place where to create the scripts folder?

 

I tried some variations, but it won´t run... I´ve got always the start-screen from your TEWS, nothing happens.Please help! THX!


Edited by Purzel
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...