Ch fighterstick pro usb and satik x52 for its throttle now…I like to see how to set the stick buttons and the throttle buttons if I were truly new, regedit issues aside. The fighterstick is almost akin to the thrustmaster buttonwise…just no 2 trigger detents and no ap slap switch, so maybe a vote to see the saetik setup though I must vote other

2 issues

1. In pit I cant see the wings of the aircraft, I see the F-16 with arms on the left wing, comming thru the wing. I dont remember the procedure of removing this from the directory, the cockpit parents file spreadsheet doesnt list the F-8, and in ckpt art folder I see a bunch of numericals before reaching F-16/18/Tornado.

The second problem is with the F-8 again. When I schedule it to be a cat bird it has the wings shown unlocked or up
or is this called folded? How do I lock them back down so I dont have them look like that in flight?

Thank you all ahead of time
-Babite

Lkdog: When you are on the controller screen in setup for the ui make sure that it doesn’t say keyboard for control mode. Then click advanced and make sure that your joystick is controlling pitch, roll and since you have a z it also does the throttle-unless you have a throttle device. Yes you want to have the control manager installed if you plan on getting another ch product or you learn to write code for the controller.
I have the CH FIGHTERSTICK USB, there are only two buttons on it that are missing. They didnt put in a 2 stage trigger, and there is no paddle switch. The combat stick has a few buttons less than the fighterstick. I throw mine into mapped mode and use a few buttons not how they were designed in the sim, until I get a throttle control I have the air brake and radar cursors mapped on the stick too, just change the mode and I have the correct stick assignment.
Hope that helps in some way

Dee Jay posted a document recently in another thread about electronic warfare fundamentals. You may find it an interersting read…as it relates to radar. I don’t know how BMS has coded the radar settings though, so I couldn’t tell you if it all works true to life, but there is a bit of an issue with radar looking through different things and can “miss” things in another altitude from the radar system. Again, I don’t know how BMS code is written or if they implement this point. But we’re all assuming you know the target wont show on your screen if the altitude of your target isn’t whats shown in the range beside or below the cursor for the radars altitude search range at that point in space.
Now when you say longer ranges, how far are you talking? Beyond 40nm?

What worked in 4.32 and should in 4.33 is when you look at the briefing screen it will show you the heading from one steerpoint to the next. If you are using Weapon Delivery Planner (thats not part of BMS software, you have to download it elsewhere) you can find it on there too.

Once within a few miles of your steerpoint you can change the course knob to show the correct arrow responces, or if you’re using the autopilot wait until after - you might loose your lunch otherwise

For some reason I can’t directly upload the TE, I’ve clicked attachments then add files and pointed it to the TE files, tried the .ini, the .tac & the .twx with the message from the manager saying invalid file. I don’t follow I guess.

Crafted another TE & tried from another airbase, just go from waypoint to waypoint using a B model. First try from Taxi selection resulted in explosion, same problem. Tried again from Take Off - exploded on runway. Its as if the wheel is rolling over an invisible mound in the runway - I didn’t know terrain had a cloaking device! So I tried again from TAXI after backing all the way out, lowering all my graphic settings to very low, comming back in & reducing trees & grass, then on the ramp I pumped the brakes a few times. To my suprise I made it from the Taxiway to the runway and was able to take off. I took advantage of this and went on a scenic tour around the airbase. When I quit out and tried again following the same procedure of trying the brakes the plane dropped to the ground again from the unseen hump on the ground. I tried again to no avail. So I deleted the F-14 flight of 1 and swapped an F-16 into its place. The F-16 was uneffected by the ground issue & performed as expected. This was otherwise the exact same TE so I’m stumped. And yes I did check to see if the wheel chocks were taken away-they didn’t display on the ground or show in my on-screen warning in either fighter.

Ok, I’ve got a small one about the HSD MFD page I noticed in TE 02 Basic Nav. I had my HSD set up the default way with the center of the circle down towards the bottom of the MFD, range displayed was 8 to the outer range ring and my NAV steerpoint was shown outside the 8 nm ring, BUT MY HUD RANGE WAS 7.x nm! I didnt have time to check my HSI for range, couldn’t get there fast enough with my mouse once I noticed it. So which display should I trust, the HUD or the MFD?

So I’ve been running both 32bit & 64bit versions of BMS 4.33, I can’t attach a crash log because I’m not crashing to desktop, just the ramp.

Can anyone else reproduce my issue with any version of the F-14 Tomcat in 4.33?

Space Bar works pretty good for that too