Posts made by Tiger 0
-
RE: 4.38
@spacee Someone knows, but like all things quantum, its state is unknown until it is known.
-
RE: F 16 Cockpit
@01mulle80 Can you get a screenshot?
Did you check your controls are assigned/working in the Setup tab?
-
RE: Viper MIP w/ MFD Displays
@drillerman52 said in Viper MIP w/ MFD Displays:
Oh right. Is it me or it is not that clear on their website?
Probably me!I agree, it isn’t clear.
“MFD” is the bezel only with the buttons, while the actual displays are “USB3.0 Instrument Display” and are a seperate component.
If you’re just buying the MFDs and displays, you need to buy them seperately, but everything is in the pack to make them a complete unit.
I really like how they did this. You remove 4 screws (you need a torx screwdriver) from the bezels and 4 from the LCDs, and then using longer screws provided, you screw the two together so the MFD is held firmly in place over the LCD. You then put the support brackets on the back of the LCD.
The displays are made by WinWing, and when booting up show the WinWing logo.
I also bought a powered USB 3.2 hub (connected to a USB C port) with the hub itself connected to a 75W PSU. The units seem to work fine like this, and I only require one USB port on my computer (the Viper MIP requires 5 USB ports - 1 for each MFD, 1 for each display, and 1 for the ICP/DED).
-
Viper MIP w/ MFD Displays
Hi,
After much research and help from several people in this forum, I ordered the Viper MIP with MFD displays last week, and they arrived today.
A quick review/critique of this package follows:
The size of the MFDs and UFCP doesn’t disappoint. The DED is very clear and easy to read, and works flawlessly with BMS (4.37 as of the time of writing), as do the MFDs and displays.
The MFD display resolution is outstanding, and the brightness, clarity, and contrast of the displays is excellent. They have a very wide viewing angle, and put my main 4K display to shame (I’m not kidding). The TGP image on the MFD is bright and clear with excellent contrast.
The buttons feel like the rubber buttons found on industrial control equipment, but that isn’t a bad thing (it just means the tactile feel is not prototypical). It should, however, mean longevity and a long service life.
Much is made of the key caps themselves being silicon, but so long as you keep your hands clean, they should prove durable.
Probably the weakest area of the UFCP is the dobber switch. They implemented it with a 4-way hat with button press, and the dobber itself is constructed from plastic, giving a somewhat imprecise feel to the switch, but the press action itself feels solid.
The units are a little too light for free-standing use on a desk (as I have it presently) but some brackets to hold them together and extend backwards to add stability would solve this. They do sell desk clamps to attach them to the edge of the desk, and the propensity for the MFDs to tip over backwards, especially when pressing the OSBs at the top, can be mitigated by supporting the top of the unit when pressing a button. The MFDs are not top-heavy however, and sit stable on the desk.
Shipping was fast (5 days) from China to the UK, and everything was very well packaged and nicely presented.
A neat feature of the MFD bezels is in-between the OSB buttons are additional buttons, that otherwise act as the dividers between the OSB buttons. This allows for mapping of additional functions without detracting from the overall look. You gain 16 buttons per MFD, for 32 in total. Useful for auxiliary switches such as autopilot control, CM switches, etc.
For someone who doesn’t have the tools to DIY, or is looking for a desk-pit (as I was), I’d say this is a solid offering, and reasonably priced, when you consider the cost of other ICPs on the market, and the cost of a small display or two for the MFDs. The DED is the icing on the cake.
Given the quality of the displays, the quality of the ICP and the DED, and the plug-and-play nature of the units, combined with the very simple-to-use software, I’d rate these a solid 9/10.
-
RE: New voice AI tools
@airtex2019 said in New voice AI tools:
hopefully we’ll never replace Lt Cmdr Stephen Hawking as LSO
I read that in his voice.
-
RE: Santa's wishlist for BMS
@molnibalage I heard that (in earlier versions, at least) aircraft landed at the wrong base will taxi along the ground to the home base, albeit it hidden. It can take them several hours to get back, as a consequence.
I think now, the aircraft are simply moved in inventory with a delay before they can be used again (I seem to recall 12 hours).
-
RE: TFR and terrain mis-match?
@SOBO-87 said in TFR and terrain mis-match?:
@Tiger-0 Different weather on the second attempt?
Same weather. It’s a TE with good weather.
-
RE: TFR and terrain mis-match?
@spooky said in TFR and terrain mis-match?:
VLC is not supposed to be used over hilly terrain, VLC is used over water/sea. When over rough terrain, don’t use VLc or you will eventually end up in a hill as you saw.
On top of that i would really recomend to check the limitations of your system in accordance with the route you are planning to fly, some turns are just impossible to make in time du eto bank angle limits and the speed you are flying at.
I was only in VLC because it kept flying at 300-400 ft even over flat terrain. It would fly higher (e.g., setting 500 ft) but not lower (e.g., setting 200 or 300 ft). VLC was desperation.
I was not turning. That wasn’t the problem. It didn’t “see” the hill immediately behind the other one, and just dived calmly into it.
I tried the flight again, and this time it flew as expected. It even pointed out TERRAIN> on the HUD, which it didn’t do during the accident flight.
-
RE: NEW WINWING ICP
@alippay2 Landing lights, master arm, laser arm, exterior lights, one of the HUD display options (e.g. night/day switch), etc.
-
RE: Can't fire gun
@drtbkj said in Can't fire gun:
@Tiger-0 I’m glad you got it sorted. Just out of curiosity, why not just use the Launcher-formerly-known -as- alternate?
Old ways die hard! I know my way around the key file, so it was as easy for me to do it manually as it is to use a tool. When I double-checked the mapping, that is when I discovered it was not mapped anywhere.
-
RE: Shooting CATM-120
@Snake122 said in Shooting CATM-120:
The CATMs in BMS I believe were first made for the Korean training theater that hasn’t came out for 4.37 or maybe the CATMs included somewhat took over that project. They were for Virtual Fighter Squadrons that wanted to do more realistic/higher volume training. CATMs allowed for shot validation and feedback, something that takes ACMI ranges and lots of debriefing in RL. So the beeps of getting hit allowed for feedback and BMS ACMI recordings of hits. This also allowed these groups to do realistic regenerations of flights so that you could still have a valuable training evolution, practice BFM/ACM/BVR and know you hit/got hit and still get an AAR and landing in instead of being shot down. I believe @AviationPlus did a few videos with that theater and may still use CATMs
I see! Very nice!!! Thanks for explaning their purpose within BMS.
-
RE: Shooting CATM-120
Before CATM missiles, what we used to do was load “actual” missiles, then use the MASTER ARM - SIM mode. This gave all the symbology and cues, but of course, pickling didn’t do anything.
CATM are supposed to be CApTive Missiles. I guess it is bugged, or not modelled correctly.
-
RE: Dogfight Override (SCOR and TNG)
@Dram said in Dogfight Override (SCOR and TNG):
Hi,
As an aside, I was pondering why TRAINING had never occurred to me. I then hit on the answer. TRAINING in UK Mil and Civ aviation is abbreviated as TRG and not TNG. Looking further, I also discovered that some countries abbreviate TARGET as TRG and not the UK abbreviation, which is TGT.
Can I assume that TNG for TRAINING and perhaps TRG for TARGET are the standard US Mil abbreviations?
A bit dry and boring I know, but appeals to the OCD part of my brain.
Regards
Dram.Seems reasonable.
I think part of the reason for the US choices of abbreviation is related to other abbreviations.
A good list is here: https://usafpatches.com/reference-shelf/abbreviations-and-acronyms/#t
-
RE: NEW WINWING ICP
@Quasi_Stellar said in NEW WINWING ICP:
@alippay2 on how to set the C/O switch. Read up in this thread about 16 days ago. It is explained exactly how to set it in the launcher. Works like a charm. For the CONT dial, I use that axis to dim/brighten my HMD
https://forum.falcon-bms.com/topic/26386/new-winwing-icp/35?_=1706572234094
-
RE: NEW WINWING ICP
@alippay2 said in NEW WINWING ICP:
@Tiger-0 thank you. I am actually setting it up. It is not hard, just few buttons are not mapped.
I have a difficulty with
- DRIFT C/O - logic is escaping me how to set it up (what is “normal” and what is “release” - for this particular set-up)
- GAIN / LVL / AUTO -> somehow I am too blind and can not find in the key mapping menu.
Regarding you question:
I used their EU store as I shipped it to Prague.
Ordered on 21.01., shipped on 24.01. and delivered today, all from Germany.General comments:
The build itself is nice, lighter plastic, but quality is good. Buttons are fine, they will last. I really like the integrated display. And for the price, it is a no-brainer.I getting back from 4.34 so there is plenty of changes. But this is too good and I have no excuses anymore.
Drift C/O - what do you mean? The hardware switch is UP for ON (meaning the TVV is fixed and will NOT show drift). Mid setting is C/O OFF, meaning the TVV WILL show drift.
“BMS - Full.key”
SimDriftCOOn 121 0 0XFFFFFFFF 0 0 0 1 "ICP: DRIFT C/O Switch - ON" SimDriftCOOff 121 0 0XFFFFFFFF 0 0 0 1 "ICP: DRIFT C/O Switch - NORM"
To assign this to DX buttons, try this:
SimDriftCOOn <DX_BUTTON_ID_ON> -2 -2 0x0 0x0 0 "DX" SimDriftCOOff <DX_BUTTON_ID_ON> -2 -2 0x42 0x0 0 "DX"
…where <DX_BUTTON_ID_ON> is the ID of the ON position of the switch when you test it in the BMS config screen, minus 1.
e.g. if the BMS config screen shows button 400, then you put 399 here.
I just had a look in the keybinds, and FLIR GAIN/LVL/AUTO is a spare switch and not implemented in BMS. I think the switch on the hardware is working though, so you can assign this to something else.
-
RE: Hook is not fully retracted
@Mav-jp said in Hook is not fully retracted:
not a bug, thats a feature
the hook is spring mounted, you can’t retract it from the cockpit alone
Is there any way to get it reset or do we need to reload to do that?
-
RE: Flares on takeoff
@SoBad said in Flares on takeoff:
@Mav-jp said in Flares on takeoff:
They are probably spotted by enemy radar at take off
Please provide TE for repro case
I doubt it. 6th day Rolling Fire campaign (not TE), Gunsan Airbase is WAY south of rapidly retreating northern troops. Red air and red A/D decimated anywhere near the DMZ. No enemy air or ground radar within 150 miles of the airbase. Also, it’s only the F-15s and F-22s that are doing it, not the F-16s.
I’ve still got the campaign file. Do you want it? Or I can video it and post the video. Let me know.
Add F-16s to a flight that YOU are NOT part of. The other F-16s are part of YOUR flight. It may be an AI-only thing, and being in your flight stops it happening.
-
RE: TFR and terrain mis-match?
@Magic49th said in TFR and terrain mis-match?:
Hi,
i don’t know of any mismatch between actual terrain and the TFR.
To judge the behaviour one would need an ACMI and the TFR settings used like ride type, cleareance, mode.cheers
MagicI’ll try and repro. It handled most terrain fine, if a little high, but this one hill was a problem. Only issue is I’m not totally sure where it was (I was just joyriding).
Setting was HARD at VLC, but it was mostly at 300-400 ft AGL. It wasn’t that aggressive nor was it really flying low, even over flat terrain. Speed was 420-450 kts.
It climbed over the first peak, descended down the other side, then didn’t seem to see the second side of the hill. It just kept flying down the side of the first hill, and crashed into the second. I realized too late it wasn’t going to pull up. It only needed to level off to clear it, then continue descending. It wasn’t as if it needed a 5 or 6 g pull-up. Nothing crazy.