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
Posts made by Babite
-
RE: Which Hotas do you use for BMS
-
F-8E Wings
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 -
RE: New User. Can't get CH Combatstick 568 USB working. Help!!
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 -
RE: High altitude radar scan
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? -
RE: CRS (course ) during navigation .
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
-
RE: F-14 A, B, D & Agressor issue
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.
-
RE: F-14 A, B, D & Agressor issue
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.
-
RE: 4.33 Issues (Known or not)
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?
-
RE: F-14 A, B, D & Agressor issue
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?
-
RE: Is the dual stage trigger absolutely necessary for BMS?
Space Bar works pretty good for that too
-
F-14 A, B, D & Agressor issue
Ive got an issue with the Tomcat on the carrier. I’ve made my own TE to ty to run the F-14 from the carrier, part of a 2 ship. It loads 4 mins from STP 1 arrival time, cant start on runway. With me so far? Here’s the fun part. Within 1 min of me being placed in the pilots seat the jet rocks back and forth & drops to the deck smoking or explodes. I tried restarting the TE, same result. Tried switching aircraft position. Same result. Tried changing mission clock time closer to TO, same thing. When I viewed it from the exterrior I see one of the MLG collapse, the jet rocks to that side, then the other side collapses.
Ok. Maybe I did something. Deleted the TE & crafted another. Different location. Tried all 4 listings for the Tomcat; the A, B, Agressor A, & the D. Start at taxi time-4 mins from TO. Again within a few seconds my jet nails the tarmac. It only happens to my Tomcat, no other flight member has that issue. For sanitys sake I tried the Hornet launch and trapping again, the Hornet has no issue for me in this reguard.
Im thinking of having the Hanger Queen tagged OOS for carrier ops until further notice, pending a test flight from an airbase may cause all wings of Tomcats to be grounded until further notice.
Ideas?
Back to confirm issue again, I had issues with my graphics card which was preventing me from doing any testing, finally got that straightened out. So I tried the Tomcat again in both 32bit & 64bit modes and have no difference with the result. I have my frame rate displaying in the pit so I can watch to see if that was an issue. Its around 15 fps on the ground when things happen, FYI 15fps is good on my machine. It drops to a claimed 2 or 3 fps when the aircraft is exploding on the flight deck, so I don’t think the issue is directly due to having issues due to FPS. And its the same every time, right side drops and then the gear seem to unlock and the aircraft drops. I get the same result no matter what position I try for. I was wondering if maybe the carrier itself was the issue so I added another flight starting feet dry, and I get the same result. I recorded an ACMI for it, is that useful or should I try FRAPS?
For reference I’m using Vista x64 sp2 for an operating system on a hp a6700y, which houses an AMD Phenom 9150e quad core processor. I added a power supply a while ago to it so I could install a real graphics card instead of the integrated chip it came with, and currently I’m running a Radeon HD 3800 for graphics. Yes I’m aware this thing is lowly but it works well enough.
I tried lowering trees & grass & no difference either.
-
RE: Bms 4.33 datalink IA…How to see them on HSD
I use IFF out or in, can’t remember which it is off hand. As BMS doesn’t deal with IFF at the moment they set that callback to be used for initiating a data link round too. And yes hold it down for a couple seconds, you should then hear a squelch noise which indicates you’re running a datalink.
-
RE: 4.33 Issues (Known or not)
[To the moderators; if this should be in tech support could you place it there?]
Back to confirm issue again, I had issues with my graphics card which was preventing me from doing any testing, finally got that straightened out. So I tried the Tomcat again in both 32bit & 64bit modes and have no difference with the result. I have my frame rate displaying in the pit so I can watch to see if that was an issue. Its around 15 fps on the ground when things happen, FYI 15fps is good on my machine. It drops to a claimed 2 or 3 fps when the aircraft is exploding on the flight deck, so I don’t think the issue is directly due to having issues due to FPS. And its the same every time, right side drops and then the gear seem to unlock and the aircraft drops. I get the same result no matter what position I try for. I was wondering if maybe the carrier itself was the issue so I added another flight starting feet dry, and I get the same result. I recorded an ACMI for it, is that useful or should I try FRAPS?
For reference I’m using Vista x64 sp2 for an operating system on a hp a6700y, which houses an AMD Phenom 9150e quad core processor. I added a power supply a while ago to it so I could install a real graphics card instead of the integrated chip it came with, and currently I’m running a Radeon HD 3800 for graphics. Yes I’m aware this thing is lowly but it works well enough.
-
RE: 4.33 Issues (Known or not)
Ive got an issue with the Tomcat on the carrier. I’ve made my own TE to ty to run the F-14 from the carrier, part of a 2 ship. It loads 4 mins from STP 1 arrival time, cant start on runway. With me so far? Here’s the fun part. Within 1 min of me being placed in the pilots seat the jet rocks back and forth & drops to the deck smoking or explodes. I tried restarting the TE, same result. Tried switching aircraft position. Same result. Tried changing mission clock time closer to TO, same thing. When i viewed it from the exterrior I see one of the MLG collapse, the jet rocks to that side, then the other side collapses.
Ok. Maybe I did something. Deleted the TE & crafted another. Different location. Tried all 4 listings for the Tomcat; the A, B, Agressor A, & the D. Start at taxi time-4 mins from TO. Again within a few seconds my jet nails the tarmac. It only happens to my Tomcat, no other flight member has that issue. For sanitys sake I tried the Hornet launch and trapping again, the Hornet has no issue for me in this reguard.
Im thinking of having the Hanger Queen tagged OOS for carrier ops until further notice, pending a test flight from an airbase may cause all wings of Tomcats to be grounded until further notice.
Ideas?
-
RE: DX
JC1;
Maybe you used the wrong key command for DMS. Up/DN/L/R should change what page your MFD is on or what display is the system point of interest. CH allows you to have 32 buttons mapped on the stick or throttle device each, I use the Fighterstick usb. I can change the mode of the stick which allows me to access all 32 buttons, even though the stick only has 20 buttons & 3 axis. 4 of those buttons I leave to be my view;so I don’t have the trim portion set up. They claim it’s possible to have ~128 buttons on the stick but you need to script them. I have my hands full with 20 as it is, there is a rocker switch on the ICP that would allow you to change the steerpoint, perhaps that is what happened or maybe you pushed the keyboard command for steerpoint increase while using your stick. DMS up should make the HUD the SOI & give you an * in the HUD, showing you that it is the display of interest at the time. -
RE: Feedback BMS-Training.pdf
So I’ve got a question re: where you want to have someone park & shut down once they land. When should it be on the ramp, when should it be in the parking area, and if there are multiple parking areas which one? I.E. TE6 where im comming in on Taegu, I don’t normally run thru Taegu and I see there are two parking areas alpha & bravo, HAS on the North taxiway and anti-blast structures on the South taxiway, and a maintenance lot. Where do I want to park since the Valet is off duty?
But nicely done. Can’t wait for the NOTAMs to start.
-
RE: Feedback BMS-Training.pdf
jc1- Guncross has been stated in my readings as the initial boom location. Your fPM will fluctuate with speed and wind, where the cross is stable. It may keep you from having to abort too; as it is usually higher than the FPM which might keep you from having the boom strike your canopy…
-
RE: Air to air refueling tutorial problem in 4.33
For me I have to keep playing with the throttle & I’ve been watching the fuel flow pph, there is no happy medium that meets at altitude x to stay at speed y position throttle & pph to z. It constantly changes & you need to keep up with it. I noticed that when I was trying to stay at a certain speed I still need to adjust my throttle position, if I don’t pay attention to it I’m either above or below that speed. I just made my own TE chasing 2 KDC-10 tankers around Korea, in a cm blk 52 loaded with 4 -120’s, 2 9x’s & 300gal tanks, and noticed that when I’m behind the power at say 270 kts I needed to have 45-4800 pph fuel flow, and I’d drop it down upon matching the tanker. Then when I finally got to 300 kts 45-4800 pph made closure way too fast, to the point I had to close the throttle completely then SLOWLY come back up. I’ll admit to using a ch fighterstick usb that I’ve started to wear the throttle switch out on.
For every action there is an equal & opposite reaction. When I push the throttle fore or aft the engine will spool up or down and the a/c will change pitch. When you change airspeed the nose will change pitch.
I do use my hud - I know, against the grain here - to watch my FPM on the horizon so I know when I need to make a correction to stay where I need to be in relation to the tanker. If the FPM moves within 2 wing lines [whatever the height of the wing is on the FPM] above or below the horizon line I need to make small correction back, if more than 2 wing lines I havent been paying close enough attention & back off a little so I dont recover into the tanker or other a/c.
And remember that the tanker lights are reversed for the F-16 as far as L&R placement, throttle light is on right & up/down is on left.
Hopefully someone finds this useful. Now make the tanker pay & offload its valuble fuel load.
-
RE: Beginner questions
Molni- When you get the tfr running normal via checks set your two ap switches then there’s a little display box higher up on the panel-click that & you should see stby in orange or adv in green/blue. This shows the tfr is where it should be when you’re using it. You’ve already set your other settings I’m guessing, so when it makes a pitch up and locks you out you press the paddle switch and have full control again until you release the switch.Its likely to happen more in precipitation so make sure you’ve set wx for tf radar. You should find paddle switch under the sidestick section.
-
RE: Preventing Issues Taxiing
You could add more static a/c on the tarmac, ground equipment, Ive never seen a tow bar used in Falcon. There are AC that magically spawn on the ramp from thin air. Yes it would cause a fps hit but wouldn’t that add to your fufillment of accuracy? How about civy ac operating in the pattern? Maybe an airbottle here and there. Even wing walkers in some instances! And nobody drops oil on the tarmac either. No spill here or there, or strips where someone locked up the brakes.
For reference I’ve tried skipping the taxi part all together and just going straight to takeoff and I’ve found myself behind a flight or two before. Dee-Jay has it right, its the job of the p.i.c. to be sure the ac is intact all the way through, from the walkaround inspection to shuting down the engine & writing your report on the ac at the end of the flight. Priority 1 is fly the jet. ATC could tell you to taxi from a to z but you have to stop when you see another ac in your path so you don’t have a ground colision. They won’t tell you that…