So some decision Points have to be made in Pitbuilding - which way to go?
BMS or DCS?
So some decision Points have to be made in Pitbuilding - which way to go?
BMS or DCS?
Why not both? They both have strengths and weaknesses.
Yes why not both? Can some of the more experienced guys with both systems explain why it would not be possible?
PS Cockpit does support bms and dcs.Is PS Cockpit open source?
No reason a sim pit can't be "interfaced" to work with both BMS and DCS.
The issue is software. All the software is currently written to read Falcon Shared Memory.
We have two options, rewrite the software we use to add an abstraction layer where you choose which Sim you want to fly and read data from, or write a program that takes data from DCS and simulates the Falcon Shared Memory, so the software already written would think the DCS data is coming from Falcon. I don't know much about DCS and how it exposes data, but I think it's all written in LUA.
I’ll look at how hard it would be to build dual support into F4ToPokeys.
I'm not trying to start a flame war here.. But.. I would think that anyone on this site putting the time, money, and effort into a sim wants the ultimate in realism. Although DCS Viper looks good and fun, well it is still DCS. They just don't have the realism and detail put into their avionics, FM ATC, etc and let's not forget the dynamic campaign. So although it is 100% great to have options, I seriously doubt guys here will be switching to DCS or worrying about it too much longer. So for sure having DCS support for our devices is a good goal, but I am certain BMS will be in our machines.
I’ll look at how hard it would be to build dual support into F4ToPokeys.
John
I'm not trying to start a flame war here.. But.. I would think that anyone on this site putting the time, money, and effort into a sim wants the ultimate in realism. Although DCS Viper looks good and fun, well it is still DCS. They just don't have the realism and detail put into their avionics, FM ATC, etc and let's not forget the dynamic campaign. So although it is 100% great to have options, I seriously doubt guys here will be switching to DCS or worrying about it too much longer. So for sure having DCS support for our devices is a good goal, but I am certain BMS will be in our machines.
After 20 + years now flying in the USAF and witness to all the various avionic/systems I respectfully disagree. Have you flown DCS lately? You can utilize an inordinate amount of systems integration and it's getting better. I think the answer will be everyone will most likely have both DCS and Falcon installed as they both offer greatness in their own respective ways. I will never uninstall Falcon but I will also be open to other sim platforms if they step up with the F-16.
PS Cockpit does support bms and dcs.Is PS Cockpit open source?
You should copy exportDCS.lua from pscockpit folder to user\saved games\Dcs\scriptsBy default DCS is looking for an export.lua in the mentioned scripts folder and calling this one first and only.
Unfortunately at the moment DCS F16 is only available in openbeta so the folder I have is user\ saved games\Dcs.Openbeta\scripts
If I put exportDCS.lua in the openbeta folder I get an error back from pscockpit (error76) saying that he can't find the file.
So I created the user\saved games\DCS\script and I have copied the exportDCS.lua in it.
Now pscockpit correctly sees the file but it gives the error LuaexportDCS.txt not found.
You should copy exportDCS.lua from pscockpit folder to user\saved games\Dcs\scriptsBy default DCS is looking for an export.lua in the mentioned scripts folder and calling this one first and only.
Unfortunately at the moment DCS F16 is only available in openbeta so the folder I have is user\ saved games\Dcs.Openbeta\scripts
If I put exportDCS.lua in the openbeta folder I get an error back from pscockpit (error76) saying that he can't find the file.
So I created the user\saved games\DCS\script and I have copied the exportDCS.lua in it.
Now pscockpit correctly sees the file but it gives the error LuaexportDCS.txt not found.
So if you are already having there an export.lua (i.e. TacView needs/creates one) either make a direct join of the existing export.lua and dxportDCS.lua or insert an "include xxx.lua" in export.lua
Good luck!
I have also copied the ExportDCS.lua in the same script folder because if this file is not there pscockpit returns an error.
Anyway I have no communication between DCS and pscockpit even if the lights in pscockpit software are green.
Ps cockpit shows green light when the board is connected.
Ps cockpit shows green light when the sim is running.
But still I have no communication between the sim and the pscockpit system
include 'c:\path\to\exportDCS.lua';
mklink /d DCS DCS.openbeta