In the “falcon bms.cfg” file "set g_fViewlimitPitchDown 0.0 " lets you look further down in your cockpit.
If that isn’t what you are looking for you can play with the curves in your tracking software.
If that isn’t it either… I’m out of ideas
In the “falcon bms.cfg” file "set g_fViewlimitPitchDown 0.0 " lets you look further down in your cockpit.
If that isn’t what you are looking for you can play with the curves in your tracking software.
If that isn’t it either… I’m out of ideas
@MailMan I had a similar problem in that after I did the update from 2.0 to 2.1, everything on my throttle (but only my throttle…) stopped working. In >User>Config I deleted all the “Setup.v100…” .xml files relating to my throttle (I had four of them as I was in 4x32 mode with my throttle), changed the throttle to DX128 mode and just rebound my buttons. All working fine since then.
@phboudreault Most useful mapping for me was mapping FOV (zoom) to the extra analogue trigger. I had the DCS switch mapped also!
Doh! That was my problem too. Mark this one ‘solved’ methinks!
I voted yes. I see BMS as remaining an F-16 simulator for the forseeable future, but if real life vipers may soon have to contend with stealthy adversaries, then we should have the choice to make theatres that represent this. No-one has to fly any particular theatre after all.
The way I see it is as a question of pure technical feasibility and how well-modelled ‘stealth’ will be.
@BVT_Gadget Also note that as of (I think) 4.36 you cannot access S-J mode while in any other mastermode (ie. DGFT override) or while on the ground (WOW) without flicking “GND jettison enable” to ON
In the “falcon bms.cfg” file "set g_fViewlimitPitchDown 0.0 " lets you look further down in your cockpit.
If that isn’t what you are looking for you can play with the curves in your tracking software.
If that isn’t it either… I’m out of ideas
@MailMan I had a similar problem in that after I did the update from 2.0 to 2.1, everything on my throttle (but only my throttle…) stopped working. In >User>Config I deleted all the “Setup.v100…” .xml files relating to my throttle (I had four of them as I was in 4x32 mode with my throttle), changed the throttle to DX128 mode and just rebound my buttons. All working fine since then.
@Cloudless From page 153 of technical manual:
“In addition 4.36 now supports 128 btn. devices. That raises the logical number to 2048 (16 devices * 128
buttons)”
So 16 full devices should work fine…
@cougar56th Downloaded, installed and seeding fine for me no issues at all. Well done for this; my first non-KTO campaign is about to begin!
Do you mean the 2d display? You haven’t specified. Using Alt-enter is a trick for moving the 2d display round your desktop if I’m not mistaken. Use CTRL-Enter if this is what you are trying to do, or go to gfx options, select ‘window’ mode, move window, reselect ‘borderless’ and you’re done.
@zappE Just quickly off the top of my head early in the AL thread on the old forum there was a procedure for uninstalling AL. You had to copy back the old HUB.exe (that you backed up into another folder, right?) and I think some other other things too. Have a search for that- I can’t remember any more right now.