Instructor position

[mac.pel]

Hi all!
I would like to do instructor position application in C# where I can read fly data(live), change weather(live), made malfunction(live) of F-16 or add opponent into flight(live). I need any foothold information it can be done.
Greetings!

[bismond]

Lightning wrote a C# library just download the .dll add a reference in VS and your good to go

https://www.assembla.com/spaces/lightningstools/subversion/source/HEAD/releases

[mac.pel]

I don't have problem with using sharedmem library
But what with malfuctions and weather ?

[Rufus]

Isn't this another one of those situations where you actually need to be able to write to shared memory?  I'd love to be able to do an instructor console in this manner...setting values to trip faults, reload armaments, fuel, etc. on the...er..."fly"... ...

[Red Dog]

you can't control weather real time with syntax lines
you can induce faults real time with the chatbox. But that's for your jet only

[raptor]

Well, chatbox opens up in-sim with a user keyboard command right? So you need the instructor program to be able (through network; ) to send a simple key command to open the chatbox, and type and run the command that point to specific failures, as these will be implemented and available through the new instructor program.

Except if there is another way to "inject" these commands real-time into the mem/sharedmem without the pilot to see any chatboxes etc opening up instantaneous, a tiny help from devs might be needed in order to actually make the chatbox "invisible", thus the pilot will not see anything in 3d..

[mac.pel]

I don't know about malfunctions in chat, thank You guys!
Where I can find malfunctions commands? I'm looking BMS documentation but I can't find anything about this:(

[-Ice]

Wow, this is interesting.... combined with something like VAC/VoiceAttack, you could effect malfunctions/faults on a voice command!

[Rufus]

...hmmnn...actually, I've faked "dual seat" operations by handing a second guy a keyboard while I was flying with my Cougar and letting him run the FCR, targeting, etc. while I fly - which sort of amounts to using two keyboards (given that the Cougar IDs as a keyboard).  So...an operator's console could have it's own keyboard which could be used to not only control cockpit inputs but also to inject fault commands; just have to take care with timing and not get the multiple keyboards in a race condition. 

What one would also need is a way to monitor flight activity - and keep track of which jet in the fray the operator was sending commands to/for.  Not sure what options you'd have for setting up camera/cockpit views on a monitoring...er...monitor...but that would/could end up looking like professional setups I've worked with in the past.

[Red Dog]

Well, chatbox opens up in-sim with a user keyboard command right? So you need the instructor program to be able (through network; ) to send a simple key command to open the chatbox, and type and run the command that point to specific failures, as these will be implemented and available through the new instructor program

Yes.
But again, at this time it sends them only to ownship. You can't send them to somebody else.

Where I can find malfunctions commands? I'm looking BMS documentation but I can't find anything about this:(

At this time this list is not supposed to be public. Because the malfunction system is not finished yet and the list isn't finalized.

The possibility to induce faults over the network should be possible in the future but the network code in 4.33 is already overloaded So I doubt it's the right time to request something like this. It will certainly come in a very distant future

[mac.pel]

 Thank You Red Dog.

[raptor]

Thanks RD. 

[Rufus]

RD - I suppose my concept would be to have an input station for each individual cockpit.  At present...would this affect network play as stands currently?

[Red Dog]

No, but then wouldn't that impact the purpose of surprise?

I mean if I'm flying my aircraft and then the chat box opens and a message is typed with a number corresponding to a fault,
1. I'll know a fault is coming
2. if I had a look at that list before; I know which fault is coming
and no, for the moment, I don't think you can type in the chat box and have it invisible or better, having it on a secondary screen, not in view of the pilot

...
So the whole purpose of the random fault being processed goes down the drain

[raptor]

Maybe "for the moment", but should be an easy code fix when time comes.