SimShaker for DCS World and Falcon BMS support thread
-
Went back and increased gain to 100% and still nothing. (AAR)
Also noticed that at the default 50%, Ground Bumps can barely be felt…. but turning NWS on/off gave a nice good bump. Increased the Ground Bumps to 100% gives a nice bump effect during taxi and it’s great, but it feels weird on the takeoff roll where it seems like it’s very smooth. On landing, I get a good set of vibrations on the initial contact, but again, the rollout feels very smooth. Maybe bring back the speed-based bump effect after a certain speed limit? 70-80 knots seems like a good starting point.
Yes, I can do that. But a transition from one method to another at 70-80 knots may be felt as abrupt and unnatural.
Another way may be adding a checkbox to let a user decide which of two methods to use. -
Went back and increased gain to 100% and still nothing. (AAR)
…. but turning NWS on/off gave a nice good bump.Looks like Airborn/On_the_Ground states are not managed correctly. I will try to sort that out. Thank you.
-
Thank you and Snake122 for the very first orders
You’re welcome, sorry for being too busy right now to help with the launch like we wanted. My schedule is brutal right now teaching high school during the day, having 3 students needing to finish their private pilot checkride before college and still having 5 other flight students on top of it.
-
Re-installed SimShaker for DCS/BMS and get the AAR connect/disconnect with no tweaking at all.
Is that correct?
Yeah, that was what I was using prior to SSWings and got the AAR connect/disconnect bumps. The installer was SimShakerForDCSW_setup.exe.
Yes, I can do that. But a transition from one method to another at 70-80 knots may be felt as abrupt and unnatural.
Another way may be adding a checkbox to let a user decide which of two methods to use.Have it start at maybe 50 knots and build up to full vibrations by 80 knots? Just trying to find a clear separation between taxi speed and runup-to-takeoff speed… I’m sometimes guilty of taxiing at around 30-40 knots if I’m not paying attention, so around 50 knots should be a good start for the transition. I know that afterburner takeoff gives vibrations due to the AB as well but in this case, I was specifically testing with MIL power takeoffs so any vibrations were based on speed/FPM/whatever.
I do like your idea of checkbox to decide between the two, but I really think having both would be a really great experience.
Looks like Airborn/On_the_Ground states are not managed correctly. I will try to sort that out. Thank you.
Can I also suggest having a checkbox for auto-updating? Some may want to stay in their current version (and thus opt out of auto-updates) until the newest version has been “tested” by other pilots. In fact, if we could have a repository of each beta release, I think that would be great so that some people can stay at a preferred version while others can test new version.
-
Can I also suggest having a checkbox for auto-updating? Some may want to stay in their current version (and thus opt out of auto-updates) until the newest version has been “tested” by other pilots. In fact, if we could have a repository of each beta release, I think that would be great so that some people can stay at a preferred version while others can test new version.
We’ll soon have 2 separate pieces of software - beta and stable, having in common just settings and registration.
All major changes are supposed to be made and proven in beta.
Current deployment tech already allows to skip an update and revert it back, just do not remove the software to be able to revert it back to the previous version.
I suppose that will cover all the suggestions. Right? -
Current deployment tech already allows to skip an update and revert it back, just do not remove the software to be able to revert it back to the previous version.
Exactly.
-
Hey Andre,
Excellent work, once again. I’m very happy with SSW
I’m testing it right now and I think I’ve found something funny.
When flying a Blk-50, the AB effect seem to kick in when NOS POS is between 20-40%, even when out of AB. The effect just starts at 20% and stops at 40%.
This with vanilla BMS, no mod whatsoever. I haven’t tested it with Blk-40 yet, but I suppose it’ll be the same.
Can you please check on your end?
Thanks a lotJudy
-
Hey Judy,
Thank you for the feedback
As we’d discussed above, there is no obvious mark in shared memory that the AB is on and no indication what a plane/block is in the action.
My current method to detect AB ON is
if (fdata.nozzlePos >= 0.2 && fdata.fuelFlow > 8000.0), i.e with fixed thresholds.
IRRC it’s correspondent to F-16B-15.I think I will add BMS specific controls to let you adjust those thresholds (fuel flow and nozzle pos ) for a plane you are flying.
I think we’ll be able to share those values between pilots here to make such adjustment easier.Any other suggestions how to solve the problem?
-
Guys,
I’ve published SimShaker - Wings beta version 0.8 with fixed AA Refueling FX.
Please test it out. -
AAR works now. Thanks.
-
Yep, back to normal now! Also, turning the NWS on/off during taxi no longer produces a bump.
-
Spacing on taxi bumps seems longer. And should it not be a “bump…bump…bump…bump” from the nose gear then main gear instead of “bump…bump…bump” that I felt? Its quite different from the old ones.
-
Yep. Looks like the old method was better.
-
Well, Andre said the new one was FPM-based?? I did notice the difference but couldn’t decide if I liked it better than the speed-based one although the speed-based one made a bit more sense. I couldn’t figure out what/how the FPM is being “bumped” but it seemed a bit random…
-
Yes, I said that.
-
-
-
This post is deleted! -
-
Hey Judy,
Thank you for the feedback
As we’d discussed above, there is no obvious mark in shared memory that the AB is on and no indication what a plane/block is in the action.
My current method to detect AB ON is
if (fdata.nozzlePos >= 0.2 && fdata.fuelFlow > 8000.0), i.e with fixed thresholds.
IRRC it’s correspondent to F-16B-15.I think I will add BMS specific controls to let you adjust those thresholds (fuel flow and nozzle pos ) for a plane you are flying.
I think we’ll be able to share those values between pilots here to make such adjustment easier.Any other suggestions how to solve the problem?
OK, now I’m a bit confused.
To be sure, I uninstalled BMS completely and reinstalled it from scratch. I now have a clean install of BMS 4.33 U3.
I’ve done some tests with different blocks and here’s what I’ve found:
Blk-52, Blk-40 and Blk-42: the AB effects behaviour seem normal. They kick in when entering AB and stop when exiting. Please note that the nozzle position is not progressive, there are no intermediate positions according to the RPM, for instance. I’s whether full open (AB on) or full closed ( AB off).
Blk-50: same behaviour as described in post #635. In this case, the nozzle position is progressive. For instance, you can find an RPM position (AB off) where nozzle position is between 20 and 40% and the SSW effects kick in.
Very strange But there must be a logical explanation…
Hope this helpsJudy