Iff you could have one thing in the next update it would be. (Archive)
-
what i Dont like in this thread is the enormeous amount of pressure it puts on dev’s shoulder and in the same time giving us the impression that you will be extremely disapointed by next release because you wont find all of this
There is NO way to make everyone happy. I look at this thread as a “wish list”. That should never mean that it is a “demand list”. Falcon has been a changing evolution since the very first mod. It continues to evolve. It’s awesome in it’s current version, so the next will continue to astound me. It will keep evolving. Becoming greater than even these petty “wish list” requests. I think everyone will be quite surprised and happy with what’s on the horizon.
-
Hi all, two technical things that I think might be useful.
I do not know if they are feasible…
First, a new keyfile parameter that send a callback when a button (state) is not down.
For example: button is down = CATI; button is up = CATIIIThis was added with little fanfare back in Update 1. Check Kolbe’s manual in your install folder for instructions on setting it up.
-
History shows that there will also be a lot of things that will be implemented although nobody asked for them, so in a way, things even out.
-
what i Dont like in this thread is the enormeous amount of pressure it puts on dev’s shoulder and in the same time giving us the impression that you will be extremely disapointed by next release because you wont find all of this
Simply NOT gonna happen! Why? Because you guys are responsible for giving us the ability to experience THE closest to real jet flight experience of all times!!!
So, whatever comes out from your - already excellent - work in the future to polish even more this masterpiece will always be appreciated by every “true” enthusiast.
So, I thank you all for what you gave us already and thank you in advance for whatever more you can give us in the future.
Best wishes for the best team out there!
Nuno
-
@Nuno:
Simply NOT gonna happen! Why? Because you guys are responsible for giving us the ability to experience THE closest to real jet flight experience of all times!!!
So, whatever comes out from your - already excellent - work in the future to polish even more this masterpiece will always be appreciated by every “true” enthusiast.
So, I thank you all for what you gave us already and thank you in advance for whatever more you can give us in the future.
Best wishes for the best team out there!
Nuno
+1
-
This was added with little fanfare back in Update 1. Check Kolbe’s manual in your install folder for instructions on setting it up.
Yes i know of the fix in Update 1. And the Kolbe’s manual is not very clear in regard to DX behaviour imho…
After testing this is what we have:SimWheelBrakes 31 -1 -2 0 0x0 0 "Activates DX31 when button is pressed and releases it when button is released
SimWheelBrakes 31 -2 -2 0 0x0 0 “Activates DX31 when button is pressed and stay ON when button is released”
SimWheelBrakes 31 -2 -2 0x42 0x0 0 “DX31 stay OFF when button is pressed and activates when button is released”
SimWheelBrakes 31 -4 -2 0 0x0 0 “If DX31 is ON releases it when button is pressed”
SimWheelBrakes 31 -4 -2 0x42 0x0 0 “If DX31 is ON stay ON when button is pressed and releases when button is released”What i mean is to have the callback executed if a DX (not the phisical) button isn’t active, without any phisical button action (example: activate CATIII if DX31 is off).
This is useful for have cockpit synchronized with controller’s switch. Maybe this have nothing to do with the keyfile and it’s a limit of something else. -
Yes i know of the fix in Update 1. And the Kolbe’s manual is not very clear in regard to DX behaviour imho…
After testing this is what we have:SimWheelBrakes 31 -1 -2 0 0x0 0 "Activates DX31 when button is pressed and releases it when button is released
SimWheelBrakes 31 -2 -2 0 0x0 0 “Activates DX31 when button is pressed and stay ON when button is released”
SimWheelBrakes 31 -2 -2 0x42 0x0 0 “DX31 stay OFF when button is pressed and activates when button is released”
SimWheelBrakes 31 -4 -2 0 0x0 0 “If DX31 is ON releases it when button is pressed”
SimWheelBrakes 31 -4 -2 0x42 0x0 0 “If DX31 is ON stay ON when button is pressed and releases when button is released”What i mean is to have the callback executed if a DX (not the phisical) button isn’t active, without any phisical button action (example: activate CATIII if DX31 is off).
This is useful for have cockpit synchronized with controller’s switch. Maybe this have nothing to do with the keyfile and it’s a limit of something else.You’d end up with the callback being continuously processed I guess.
Your other option is to just wire your switches so that they are ON-ON switches.
-
@A.S:
The planet is poisoned by “cash” … no need to kill BMS too …stay FREEEEE
Please can I have some poison ?
I promise I’ll only kill me self.
-
Hi all, two technical things that I think might be useful.
I do not know if they are feasible…
First, a new keyfile parameter that send a callback when a button (state) is not down.
For example: button is down = CATI; button is up = CATIIICorrect me if I’m wrong but every time this “button” is polled then a state or action will be continually set/repeated, I don’t understand what possible use it would be in this kind of software environment. Default conditions are usually set when a program initializes.
“Buttons” are either 'NC" or NO" (normally closed/open) and if used as inputs for a logic device of some sort are polled in sequence for a change of state. Are you building a cockpit ?
-
You’d end up with the callback being continuously processed I guess.
Your other option is to just wire your switches so that they are ON-ON switches.
This is exactly what i don’t understand.
If i have an ON-OFF switch with an assigned DX to its ON position and i enter the simulation world with this switch ON
the (active) DX is immediately recognized. (Is then continously executed…? )Maybe this same behaviour can be used for a not active DX? Probably it’s due to how the code work.
-
Correct me if I’m wrong but every time this “button” is polled then a state or action will be continually set/repeated, I don’t understand what possible use it would be in this kind of software environment. Default conditions are usually set when a program initializes.
“Buttons” are either 'NC" or NO" (normally closed/open) and if used as inputs for a logic device of some sort are polled in sequence for a change of state. Are you building a cockpit ?
Nope, i’m working on a Warthog profile and i notice this behaviour, so i thought it would be useful to have this possibility.
-
This is exactly what i don’t understand.
If i have an ON-OFF switch with an assigned DX to its ON position and i enter the simulation world with this switch ON
the (active) DX is immediately recognized. (Is then continously executed…? )Maybe this same behaviour can be used for a not active DX? Probably it’s due to how the code work.
the DX press is constant. Falcon interprets it but sends the callback just the once till the switch state changes iirc.
No need for more than what we have with ramp starts tbh. You say you are concerned about controls being synchronised with the virtual cockpit, but this is no longer a problem with the advent of callbacks for specific switch positions.
-
Tragic! lol
Yes, that’s tragic. Many cable provides simply don’t give any IP v4 adress anymore. I’m stuck with selecting a cable provider with IP v4 instead of selecting the one with the best bandwidth just for BMS.
On the other hand, do you have a workaround for that problem?
-
Yes, that’s tragic. Many cable provides simply don’t give any IP v4 adress anymore. I’m stuck with selecting a cable provider with IP v4 instead of selecting the one with the best bandwidth just for BMS.
On the other hand, do you have a workaround for that problem?
BMS should use a free text input. IpV6 should be handled by the underlying OS and doesn’t necessarily need changes in the application itself.
-
do you have a workaround for that problem?
Maybe, try Hamachi. (?)
-
-
That means one could use Hamachi to obtain an IP v4 adress? Would be worth a try.
I just hope that I get an IP v4 adress at my new home. Will see in november… Thanks for the hint!
Let us know - If it works with Hamachi.
-
Well it should work but then you have bw overhead problems… meaning more bandwidth needed to send the same amount of information across the network
-
Id like to see the ability to select DTOS when on the ground, and to be able to slew the DTOS cursor around the HUD with WOW active.
-
Complete the external lighting, formation lights, refuelling light, dimming, etc…
Cheers
Tulkas