Amadeus75
@Amadeus75
Proud member of the "49th Black Diamonds", although mostly too chicken to fly online.
Falcon 4.0 crashpilot since 1999 (version 1.04)
Classic rock keyboardist, Pink Floyd fan, newspaper graphic employee.
Best posts made by Amadeus75
-
RE: 4.37 Screenshots
Memo to myself:
“Just because I frag the tanker, does not mean I’m the only one who can use it.” -
RE: Your screenshot for our Falcon BMS website and BMS install
Very cool, Micro.
I may make a start with my best try. Good luck! -
RE: weird clock
They fixed the clock!!!
And I haven’t noticed it until today
Could not believe my eyes! Thank you, thank you, thank you!!! -
RE: Best voice command software or profile?
@Atlas
I can’t speak for DCS, but of course there are numerous voice activation programs availabe and many gorgeous profiles.
Take a look into the “Joysticks & Input Devices” section:
https://forum.falcon-bms.com/category/28/voice-controlI use SemlerPDX’s profile for VoiceAttack, which contains all available callsigns used in BMS… and can be used not only for radio comms, but also for doing lots of other stuff.
Never want to do without it again. -
RE: the sea burns
Maybe a compromise?
Let it burn for 20 sec and then let it extinguish?
Just a thought. -
RE: AVCS4 Immersive Voice Control Radios for VoiceAttack
Dear @SemlerPDX,
may we look forward to a little AVCS4 update, due to the additional radio calls
(“weapons free A-A”, “weapons free A-G”)?
Best regards -
TGP issue: BMP-2 remain white dots in BHOT mode
With 4.36, I experience an unexpected behavior with the BMP-2 model.
I created a quick TE to practice LGB delivery.
The target is a tank bataillon consisting of several T-72s and BMP-2s.
Watching the units via TGP, and toggeling WHOT/BHOT, the BMP-2’s remain white dots instead of turning black dots.
All other units around them are displayed correctly - it’s just the BMP-2s inbetween that make irregularities.If you close in to the bataillon and/or if you zoom in, they normalize and turn black as expected.
KTO theater, standard weather, clouds.
Tried with and without smart scaling.
-
RE: Voice Attack PTT, UHF/VHF ?
@Sabre
I have bound VoiceAttack to my UHF button, and I am very happy with this decision.
For me, this makes best sense when flying with human buddies.
On the one hand, the VHF channel remains unaffected. On the other hand, your human wingmen can actually hear you ‘talk’ to instances like tower, approach or AWACS.For instance, I say to AWACS,
“Hey Magic 4, this is Hawkeye 41, have you got a picture for me?”VoiceAttack recognizes “picture” and types “Q-1”.
But my (human) flight members think, “whoa, there’s a real conversation going on!” -
RE: No taxi/landing lights with U3
@seifer
Thanks a lot for the explaination - I am totally reassured. Makes perfect sense now.
Shame on me that I did’t try at night first.
Actually, when flying with an AI wingman, I got used to keep an eye to him -
whenever he turned on the taxi light, it was kind of a “ready to go” signal from him. That’s why I missed it so much at first.Altogether, the enhanced lighting system is lovely, and so is the fresh new coloring.
Gives me +20 % more happiness when flying
Thanks a lot for you countless hours of work.
Latest posts made by Amadeus75
-
RE: No wingman's voice over radio when online
@Dukera Very nice! Shine on!
-
RE: No wingman's voice over radio when online
@Dukera
Do I understand you correct: the power failure messed up your internal IP address?
If your internal IP was fixed, there wouldn’t be any need to change the portforwarding Just make sure your PC has the same internal as it had before.In game - in 2D - can you perform a comm check with “F1” (UHF) and “F2” (VHF), and do you hear each other here?
Last not least… make sure you share the same frequency.
When flying with my buddy, we ALWAYS have to double-check before flight if we have the same preset 1.
All the other presets are perfectly synced… but preset 1 differs most of the time, I don’t know why. -
RE: Viper TQS Calibration procedure
@Scotters
I do not use the virtual buttons.
With the new BMS launcher and the “press” and “release” logic, there is no need for them.
I don’t know about other sims… but if it’s just for BMS, then better keep it simple. -
RE: Viper TQS Calibration procedure
@Scotters For me, the best way to ensure a positive calibration result was:
Keep pressing #5 while pluggin in and confirm that all the TQS lights stay dark.
After a couple of seconds, release the button and confirm that all lights turn on.For my understanding, that is the “ready” signal for the calibration.
-
RE: Viper TQS Calibration procedure
Update!
I was able to solve my “button 18 displacement” with this calibration procedure - thousand thanks to @benco!Took me a couple of tries.
But I figured out that at the start of the calibration you probably need to keep button 5 pressed WHILE pluggin in.
Or simply keep pressing button 5 for longer than 3 seconds.Either way, I am relieved and happy
Thanks again mate!!! -
RE: Viper TQS: Button 18 actually in the wrong place
Solved the problem!
Thanks to @benco in his post Viper TQS Calibration procedure
I was able to fix the DX 18 spot with the calibration after a couple of tries.
The magic trick to get the calibration to work is -- either to keep button 5 pressed WHILE pluggin in
- or simply press button 5 longer than 3 seconds.
Either way, you get no visible feedback that the calibration is in process, so you always have to guess and try.
See you in the sky, folks
-
RE: Viper TQS: Button 18 actually in the wrong place
@skippermike Thanks for checking, and appreciate your input. Apparently this is nothing I can fix for myself.
Looks like I will have the set replaced. -
RE: Viper TQS: Button 18 actually in the wrong place
@oakdesign Thanks for the hint.
But the zone on the rail between “off” and “idle” is physically not part of the axis
If it’s not for button 18, then the idle detent bump is of no use at all. -
Viper TQS: Button 18 actually in the wrong place
Gentlemen,
yesterday I started a call for help in this topic:
Viper TQS Calibration procedure
… but I feel uncomfortable in hijacking a thread.
Besides, it looks like it’s a new Viper TQS issue I have not seen before on the forum, so yes, I would like to open yet another thread.The topic itself is well-known… it’s the idle detent… BUT:
I understand and appreciate the PRESS and RELEASE logic.
I understand the cutoff is not a part of the axis, but a seperate button (DX 18).
But I also assume that the very “trigger position” of DX 18 should be right on the CUTOFF position.In my case, DX 18 is triggered on the IDLE position, of which I think is wrong.
Every time I pull the throttle back to idle, I can see
(in the launcher as well as in the device properties)
that DX 18 is fired… although I would it expect to be triggered inside the “off” zone.My inquiry to the TM support is on its way.
For now, I would like to know- if my understanding is correct at all
- if the position of DX 18 can be calibrated
- if this is a hardware issue
- if this is a firmware issue (I have 1.26)
- if this is a driver issue (I have 1.2.3.0)
… anyway, if the nice looking device is going to be returned to sender or to be replaced.
Please let me know if somebody else has a familiar issue or a piece of advice what I could do to get the DX behind the detent.
Cheers everyone! -
RE: Viper TQS Calibration procedure
@benco
Thanks a lot for this procedure!
Unfortunately, I have an additional enigma here, and I hope somebody can help me out.Yes, it’s the well-known IDLE DETENT story.
I understand and appreciate the “PRESS” and “RELEASE” logic. But what I definitely do NOT understand is this:The tiresome BUTTON 18…
… the “trigger spot” should be located right BEFORE the bump, right?
I mean, inside the “engine-off” area.In my case, it is located (and triggering) exactly at the IDLE spot - actually AFTER the bump.
Can this be correct?
Can this be corrected?
I read in the calibration PDF file, that button 19 (the AB detent) can be fine-tuned by hardware.
But can button 18?Latest firmware 1.26 is installed…
EDIT - I opened a new thread about this issue: Viper TQS: Button 18 actually in the wrong place