Air brakes ?
-
…
…for a new UI libWith the advances in hardware in the last 15 years you could really save yourself some time and do this in a .net or CLR language then wrap it up for presentation to C++ There isn’t anything really “Time Critical” in the UI that requires you to stay with the unmanaged languages, and you can pull the other APIs and DX out of the UI altogether–much cleaner and easier to manage since you aren’t actually transitioning to 3D from an in engine UI. It’s simple enough to call the managed code from the C++ loop, and plenty of articles on the interweb to help get you started too–added bonus you can use it to call your 3D window and do garbage collection after the fact to catch any leaks in the spaghetti. Just a thought…
-
-Vandal-
I hear what your saying but here’s the thing
Most of the CFG Vars options that are not available are old and obsolete some work some don’t and believe me there are a lot off options in the code and going though the list to see if they work or not is no quick job and I don’t have the time due to coding other things.
adding those to a MP check for a tournament scenario would be a real PITA and take time of a coder to implement when he could be working on something else for example I’m in a learning curve for a new UI lib and doing little other fixes others are doing other things which have been asked for 4 ages a lot of new things coming
so this would be very, very low priority if on the list at all.
I don’t see it as taking away options as you didnt know it existed before I posted it and those other ones were removed in our ongoing attempts at making this primarily F16 sim as real life as we can get it…
I will however help those as much as I can such as the OP and others
Bahh Dee-Jay was quicker at typing
LOL on Dee-Jay beating you out. But for the record, now that I am learning how to build button boxes and a rudimentary pit, I’ll be able to make my own indicator that I can see. So, I really wasn’t asking on behalf of myself. But what is that saying? “When they came for X I didn’t speak up… and when they came for me, no one was left to speak up?” Something along those lines. There’s no telling what sort of crutch or feature you and I may need or want in the future. So, I am just speaking up for the idea that taking stuff out “for realism’s” sake alone is not necessary and may impede someone’s ability to enjoy this sim. I completely understand about debugging, incorporating new blocks of code, etc. and wanting to get your priorities taken care of. I won’t fault anyone for that, but again, if it’s not too hard please consider keeping and reinstating options.
-
@JJO:
@Stevie, that looks like ghosting on the switches. Programming the speedbrake can be easy done with XKEYS. Closed should be programmed as steady switch (release is the middle position) and the speedbreak open is a momentary switch. With the momentary function you can open the speedbrake step by step (or hold to open full)
What interface do you use for your pit ?
Yes - exactly; I do use a steady switch for close and that’s the problem in conjunction with pedal brake - I get hook cycling (key collision) when both are hot…so I simply time the close switch out (null input) after four seconds, parking problem solved.
I’m using Pokeys for my pit, but with my FAF Mac setup I use a utility called ControllerMate that makes short work of programming these sorts of things out at the input level. REALLY wish there was a version of ContollerMate for the PC…it would be all I’d use when it comes to USB devices.
-
I am not familiar with Pokeys, check http://xkeys.com/PIComponents/index.php for info about the XKEYS. You can use it for keyboard/mouse and joystick functions. My pit uses original cables from the panels. so that means hundreds of meters cables. The little pcb does it all The PCB will solve your ghosting problem.
Buying from Europe is expensive, within the USA the shipping is much cheaper.
-
Heh…other way around for me, as we have to get Pokeys from the Continent!
https://www.poscope.com/product/pokeys57u/
Yes - I know about X-Keys and gave up on them after realizing they only do hard switch inputs, and I would be needing to cover switches, pots, encoders, outputs signals, etc. Pokeys allow me to do all of that using one board, and are a bit easier to deal with that Arduino from a programming standpoint, IMO. I want to use a single type of board in my pit build, so I’ve gone with Pokeys…but was a close race between Pokeys and Arduino for a bit. I may still try an Arduino Micro with my ICP…maybe.
-
I raised the volume of the airbrake sound file and now I have no doubts about its position, and I think it is more realistic too.-
where do you do that? file please
-
where do you do that? file please
sound effects slider in set up screen - but don’t put it up too loud or you will drown out the tower commands especially when you drop your landing gear as well …
-
and I think it is more realistic too.-
Wrong assumption. Airbrake are completely inaudible deceleration and only felt at high speed. No vibrations.
-
If using COUGAR airbrakes switch is a momentary switch for extending(return to the neutral position if you release the finger) but is also an alternate switch for retracting(does not return to neutral even if you release the finger).
Same for WARTHOG. So always keep the speed brake switch to retract position is a good habit to have.For any non-cougar user, this does not work…
-
That could work…in theory…unless it causes key collisions, which mine seems to. Having the speed brake switch in close and hitting my toe brakes during landing roll out causes my hook to cycle. So I get around that by timing out the speed brake->closed signal after four seconds; that’s the rough time I counted it to take the boards to go from full open to full closed. Works for me…
-
Keyboard emulation causes the command collision. I recommend DX bindings as possible.
Well, I meant Saitek nor CH may not have <on>-OFF-ON switch ( <on>snaps back, ON keeps its position) but only <on>-OFF- <on>switches so they can’t keep SPDBRK position to retract ON.</on></on></on></on>
-
Yes - depends on your setup…but be aware.