questions on support for pitbuilders

[ruprecht]

Couple of quick ones:

 

1. Will all cockpit functions be available with keymappings?

2. Will all keymappings be discrete (e.g. one for gear up and another for gear down) rather than toggles?

3. Will it be possible to run the ABRIS and Shkval displays on additional screens or on a LAN-linked PC display?

4. Can we get access to the keymap and panel map (i.e. what switches are on what panels, what they are for and what type of switch they are e.g. on-on-on toggle or locking pushbutton etc) in advance of release so that we can start building panels for our cockpits?

5. Will multiple controllers be supported? e.g. can I have an X45, an X52, CH pedals and Saitek throttle quadrant, plus other HIDs up to the Windows limit (e.g. BetaInnovations Plasma) all mapped to different axes?

 

Thank you!

Edited July 9, 2008 by ruprecht

[Renato71]

Lets not forget documented support for outputs! Some people are working for quite a long time to enable outputs, and it would be much faster and reliable if there is documented support. And I do not mean something like "plain list of lua commands" or "go learn lua" replies.

[Triggerhappy69]

Lets not forget documented support for outputs! Some people are working for quite a long time to enable outputs, and it would be much faster and reliable if there is documented support. And I do not mean something like "plain list of lua commands" or "go learn lua" replies.

 

 

You mean something like this:

http://G:\Hobby Files\IOCards Files\LOSIOC\LOSIOC Tutorial.mht

 

 

LeCreole have been working on this for quite some time now.. I have translated the old LOSIOC program from french to english. Send me your e-mail adress and I'll send you the old one.. The new one I think they are working on translating to both english and spanish as we speak..!

 

More on the 3rd Wing's developer forum.

http://www.3rd-wing.net/index.php?showforum=72

 

The guys in the 3rd Wing squadron does some pretty damn impressive work on both pitbuilding and add-on software developing! I salute them!:thumbup:

[ruprecht]

So the latest development update partially answers Q3, as the Shkval can be run on an additional screen on the same PC. I have seen elsewhere that the dev team plan to release the flight manual in advance of the sim, so that partially answers Q4. Otherwise I'm still in the dark, anyone?

 

And Renato you're right, "go learn LUA" is not an appropriate answer to questions about outputs. We need to know what data elements are available from the sim before we can write the code to map it to our output hardware using LUA etc.

[Renato71]

You mean something like this:

http://G:\Hobby Files\IOCards Files\LOSIOC\LOSIOC Tutorial.mht

You realy are "triggerhappy" - link is local :music_whistling:

LeCreole have been working on this for quite some time now.. I have translated the old LOSIOC program from french to english. Send me your e-mail adress and I'll send you the old one.. The new one I think they are working on translating to both english and spanish as we speak..!

 

More on the 3rd Wing's developer forum.

http://www.3rd-wing.net/index.php?showforum=72

 

The guys in the 3rd Wing squadron does some pretty damn impressive work on both pitbuilding and add-on software developing! I salute them!:thumbup:

 

Yeah, thanks to you I understand more about that project. But my French is a black hole, and using babelfish or alike is not a real solution.

 

And Renato you're right, "go learn LUA" is not an appropriate answer to questions about outputs. We need to know what data elements are available from the sim before we can write the code to map it to our output hardware using LUA etc.

 

Yeah, especially frustrating to people like me that have no knowledge about LUA :(

On the other thread I've asked for option to create a backup of mp_log. Mugatu was a great help, and while he was replying (and writing from head) I was able to spot an error in his script - damn I was proud of myself! And for a dude like Mugatu - this was a piece of cake. And LUA itself is not well documented at all. Before I asked above question I spend several days reading official LUA documentation. No comparison with the way VB or C++ are documented!

LUA should be documented in the way that is end-user-friendly, or more correctly to say "DCS customer friendly". It is in ED's interest to document at least those parts that are related with FC/DCS, not just to provide some list of comands and say "here you go".

Positive replies to your questions and official support for "gadgets" will kick the pupularity of FC and DCS skyhigh! Flying models are amazing, visual effect magnificent, and if they could myke pit building easier it would truly make DCS one of a kind, without any competition at all :D

 

Russia is doing great with fine tooling and luxury comodities lately, and the prices are acceptable. There is no reason for ED to sponsor/support/assist some outside company in production of "authentic" gadgets. THey do not have to produce those by themselves, just to test it and declare it officially approved :smilewink:

Just look at all those ready-made gadgets (panels, swithces...) for FS - I want those for my FC (and BS) :cry:

[Renato71]

PS - I wrote my previous post about 15 min prior to official annoucement by Wags of following:

Physical Cockpit Interface Package (PCIP). This package provides support to cockpit builders and allows them to more efficiently, and with great depth of capability, to port systems simulated in software to their physical cockpits. This includes support to various projection systems. PCIP will be made available to all after the release of DCS: Black Shark.

 

YIPIEEE

[ruprecht]

bump for an official answer to the OP please! Wags's post on the PCIP implies some answers to some of those, but a direct and unambiguous answer would be very much appreciated. Thank you!