DCStoF4 (Standalone version)

[SharkNoir]

Yes

[Red Dog]

great stuff, still use it everyday.
I'll have a few question to bother you in the coming days

[Red Dog]

I know I may ask the arm ...

What about mag switches?
Obviousy these don't work with DCStoF4 because eventhough the shared memory is active, the state of say the JFS switch does not change in BMS when you activate the DCS mag switch.
Yet a Im using the same keystroke within DCS and BMS.
Is there any way to change the sharedmem state of a bit with a keystroke? (Since that usually comes from BMS after the relevant keystroke as well)?

I know I know.... But maybe there is a way ...

[SharkNoir]

Hello,
So on DCStoF4, I'm simulating the magnetics for :
- JFS "JetfuelStarter".
- Autopilot "AutopilotON".
- Parking brake 'ParkbrakeON".

I need to test for FLCS bit "FLCSbitRun".

So sure, it's not perfect because it's far from BMS extractions and DCS only focuses on VR.
For the moment, magnetics are simulated in relation to light and switch states.
But for me, it works even in external view.
You can keep your arm...

I'm on 1.20 of the script but 1.18 already worked.

Can anyone confirm this?

[Red Dog]

...my pit only starts to react after I switch the UFC switch (AVN PWR) to ON at ramp. Before that nothing works.
But once past that it works great and saves a lot of DCS specific programming which is a real hassle when you developed your pit for BMS shared mem.

Update on that issue.
Thanks to Sharknoir's help this issue is finally identified.

The way my script.lua file was done, Simshaker was declared after DCStoF4.
Olivier corrected my script.lua and moved my Simshaker declaration below the F4toDCS declaration

Now F4toDCS works great immediately upon entering the pit and I don't have to wait till switching the UFC switch to ON for my pit to come alive in DCS.
Side effect is that SimShaker now doesn't work anymore in DCS.
but we're working on that

I think I had similar issues with Helios before with the order of the declarations of the script file.
Very touchy to make all these external software work alongside each other.

Thanks Sharknoir for your unlimited support with this

[Deadhead]

Exactly what I need.
I was struggling to find a way to use my arduino dcs bios based ded for both dcs and bms.
After finding out deduino and this piece of software existed I immediately switched over to deduino.

Thanks!

[questerymj]

I have a problem here, I try to use DCS to F4 with F4TS(F4 to serial) , I try to merge the scripts of both export.lua but looks like it didn't work, once I add

local xflight=require('lfs');dofile(xflight.writedir()..[[scripts\DCS-XFLIGHT\Util-Dial.lua]])

into the export.lua of F4TS it stop work/communicate with DCS, I change the port from 8081 and 8082 didn't help, does there any way to slove this?

[SharkNoir]

Hello,
Why do you want to merge the 2 export scripts (F4TS & F4ToDCS) for DCS?

Have you tried setting up F4TS for F4 BMS?
Start F4BMS on the menu page.
Start F4TS.
Then start F4ToDCS and DCS.

I can't use F4TS because I don't have the hardware to run the application. It's stuck on the serial port settings.

[questerymj]

Thanks for reply Shark! I really appreciate your DCS to F4.

The story is I'd build a CPD for bms and I try to use Yame64 with DCS F-16. At the same time I use F4TS to build the warning light sets because it support lightbit matrix to maintain 64 light output for BMS and DCS at same time, it's very handy for me. I had tested and it works well for BMS and DCS both.

But F4TS and DCS to F4 and Helios all need to use export.lua to communicate, so I try to merge them together. So far my test result is:

Helios+F4tS=ok, lightbits export worked
Helios+DCS to F4=ok, I can use CPD from Yame64 with DCS F-16

But if I add the declare line of DCS to F4

local xflight=require('lfs');dofile(xflight.writedir()..[[scripts\DCS-XFLIGHT\Util-Dial.lua]]))

into the export.lua, both of F4TS and DCS to F4 won't work. I don't know if the port conflicted (F4tS use 8080, DCS to F4 use 8081 and 82) or other problem and change the order didn't solve the problem. I'd attach the export.lua I use now (it's basiclly export.lua of F4Ts+declare line of DCS to F4 and Helios, F4TS didn't use dofile way), wish you can take a look if possible.

Thanks for your genius work!

[questerymj]

So far I'd successful to use yame64 with DCS F-16 The third TM MFD is installed for F/A-18 and F-15E

[Red Dog]

Wow, that's quite an export file
I'm interested to know more about the why's and the how's ... As I need to reactivate my screen and which to switch back to Yame from Helios for DCS

Glad to see more ppl use this app, it's a real gem for us coming from BMS and flying DCS. or for us flying both.
It saves a lot of pain interfacing a cockpit for multiple sims

once again @SharkNoir : merci beaucoup

[questerymj]

I would like to suggest to use Helios for DCS instead YAME or other screen porting software for BMS, there are already enough F-16 cockpit parts in Helios tool box. The unqiue instruments I still wish to export from YAME is CPD and ATD+， unfortunately ATD+ doesen't work with 4.37 so I make a fake one by Helios.XD

[Red Dog]

yes, the reason I favour Yame is indeed the CPD

[questerymj]

BTW I feel the fps of CPD via DCS to F4 is somewhat low(50% when playing BMS) , maybe because my PC is old... or other way to improve this?

[SharkNoir]

Hello,
New version of the software available on the share page.
Version 1.22 for scripts.
Version 1.0.1 for the executable.

Corrections :

• Addition of some DED pages
• Correction of the LASER page
• Correction of CMDS for Chaffs and Flares
• Addition of FLCS indicators A B C & D

Thanks to RedDog for the feedback.