Bonanza: so many issues
-
I have to say I'm pretty disappointed with the Bonanza. While it looks like an absolutely great product my whole experience so far has been nothing but frustrating. I have yet to get her off the runway. I have flown the mod improved G36 a lot before, so I should know what I'm doing. I've tinkered with it for the last couple of days but there are so many issues that nobody else seems to have.
- I have huge trouble starting the turbo version. I'm following the checklists but the engine won't start. A cold engine should start after priming it for 3-4 seconds, right. Well, I have to prime it for like 10 seconds, often multiple times, to get it to start. That shouldn't be right for a cold engine.
- State saving is not working at all. Every variant just loads in it's default configuration with the weather radar on standby and all switches on off, no matter in what stage I last leave this particular plane in.
- I've had multiple occasions where the plane was glued to a ground after setting/unsetting the parking brake and wasn't able to move at all, even after applying full throttle. I tried slewing the aircraft to a different position that didn't help, it made things even worse, as the plane was now shaking and wobbling but still glued to the apron. I have to restart my session.
- I'm using Spad.Next and I know that the bindings for the magnetos have been changed in the latest version. But I should be able to use the default events like MAGNETO_OFF, MAGNETO_LEFT... Doesn't work though. I also wasn't able to bind Mixture in the Turbo, though I might have to read the manual again as I know you guys use a custom Mixture system.
- Is the plane using WASM that needs to be compiled after installation or an update? It took like 20 minutes to load my very first session and even more time to load after updating to v1.1. Subsequent sessions loaded faster, but still a lot slower than every other plane. This might be related to MS server issues though, I'm not sure. MS servers seems to have issues lately.
-
- I have had no issues starting the aircraft. Quick and easy start . All levers full forward. Fuel pump on LO 3 seconds the off. (check you have fuel pressure). Throttle full back then 1/2 forward. Start. Should start up no problem.
Are you starting with no fuel? Is your fuel set to cut-off? Are you flooding or starving the engine? What are the weather conditions where you are at? This makes a HUGE difference. Be more specific.
-
Save state as far as I can tell doesn't work for me either, but I am so used to closing out MSFS with the "X" I just might be neglecting that fact you have to close out of MSFS from the main menu and selecting QUIT. (if you are not doing that it WILL NOT WORK....). But like I said, I havn't closed it down properly yet. I am in a flight right now, when I end it if I remember I will test this.
-
Have had no issues being STUCK. Are you trying different airports? Is it aftermarket scenery or default? Have to tried starting on the runway? If you havn't done any of this you can say its for sure the aircraft and not the location you are at.
-
MAG issue I believe was fixed in 1.1.
-
I have had no unusually loading times. Remember ANYTIME you remove or add something to the community folder it might take time for MSFS to register/process it, specially for scenery. Do you have PMDG, FENIX, or FBW aircraft installed?? These could be the issue as they do take longer to load after updates.
You can say "so many issues" if you haven't made sure it was the aircraft.
-
@petze said in Bonanza: so many issues:
I have to say I'm pretty disappointed with the Bonanza. While it looks like an absolutely great product my whole experience so far has been nothing but frustrating. I have yet to get her off the runway. I have flown the mod improved G36 a lot before, so I should know what I'm doing. I've tinkered with it for the last couple of days but there are so many issues that nobody else seems to have.
- I have huge trouble starting the turbo version. I'm following the checklists but the engine won't start. A cold engine should start after priming it for 3-4 seconds, right. Well, I have to prime it for like 10 seconds, often multiple times, to get it to start. That shouldn't be right for a cold engine.
- State saving is not working at all. Every variant just loads in it's default configuration with the weather radar on standby and all switches on off, no matter in what stage I last leave this particular plane in.
- I've had multiple occasions where the plane was glued to a ground after setting/unsetting the parking brake and wasn't able to move at all, even after applying full throttle. I tried slewing the aircraft to a different position that didn't help, it made things even worse, as the plane was now shaking and wobbling but still glued to the apron. I have to restart my session.
- I'm using Spad.Next and I know that the bindings for the magnetos have been changed in the latest version. But I should be able to use the default events like MAGNETO_OFF, MAGNETO_LEFT... Doesn't work though. I also wasn't able to bind Mixture in the Turbo, though I might have to read the manual again as I know you guys use a custom Mixture system.
- Is the plane using WASM that needs to be compiled after installation or an update? It took like 20 minutes to load my very first session and even more time to load after updating to v1.1. Subsequent sessions loaded faster, but still a lot slower than every other plane. This might be related to MS server issues though, I'm not sure. MS servers seems to have issues lately.
Here are some answers point by point. Hopefully these might help alleviate your issues, issues that aren't shared by others at the moment.
-
The turbo version and the normally aspirated version start identically. If you have not bound the mixture correctly for the turbo version, then it stands that it might be hard to start with the mixture at idle/cutoff.
-
States are saved on a per-variant, and per-livery basis using the new native state saving mechanism. Some users have reported this feature not working on their computers. The issue is most likely with file permissions, anti-virus, or perhaps something with MSFS itself.
-
This also has nothing to do with the aircraft, it's been reported for many others a/c in the past including default.
-
All magneto and starter input events now work with v1.1. The mixture can be bound with the in-game mixture axis, or any of the following key events: MIXTURE1_INCR, MIXTURE1_INCR_SMALL, MIXTURE_INCR, MIXTURE_INCR_SMALL, MIXTURE1_DECR, MIXTURE1_DECR_SMALL, MIXTURE_DECR, MIXTURE_DECR_SMALL, FUEL_Mixture_1_Rich, FUEL_Mixture_1_Cut, MIXTURE_RICH, MIXTURE_LEAN, MIXTURE_RICH, MIXTURE_LEAN, MIXTURE_SET, MIXTURE_AXIS_SET_EX1, AXIS_MIXTURE_SET, MIXTURE_SET, MIXTURE_AXIS_SET_EX1, AXIS_MIXTURE_SET. You can also set the L:Var "L:BKSQ_MixtureLeverPosition_1" from 0-100 if that's easier. The only method that does not work is the Asobo discouraged method of setting the A:Var "A:GENERAL ENG MIXTURE LEVER POSITION:1" directly.
-
No, the aircraft does not use WASM, and no loading time increase has been noted during testing. In general, Black Square aircraft load faster and have better performance than aircraft with large glass panel avionics, because the loading and rendering of geometry and animations is significantly faster than that of WASM or JS avionics.
Hope that helps. If you feel issues persist and you require further help, please contact the support team and they'll do what they can to help.
Thanks for your custom.
-
Yes, I'm doing all the steps from the checklist, double checking everything, moving the controls with the mouse and not with the hardware, without any other addons... But the engine is not starting most of the time.
Thanks for your help, but I'm giving up. I've spent so many hours over the last days trying to get this thing running from cold and dark, it's not fun anymore. I even recorded my whole startup procedure but now I would need to spend some more time on reducing the file size of that video and finding a way to upload it here. It's just not worth it.
The analog overhauls look like a great product line and I'm all up for improving the default airplanes but I guess the Bonanza wasn't for me. I happily consider my 30+ bucks as a donation for developing further overhauls but this is the end of the line for me. There are other planes like the 310 or the 414 which are way more fun to fly than this thing, at least for me.
But thanks again for trying to assist.
-
@petze That's a shame and your situation is very rare as there have been minimal operational issues for this a/c and zero refund requests as things stand. The skies are fully of happy Bonanza flyers currently with you being the exception.
We really don't want you lumbered with something you've paid good money for and are unable to use. Can I not suggest you open a ticket with our support team and get them to try and help you. They'll also liaise directly with the developer to try and find a solution for you. Is this not an option for you?
Support team can be reached here: https://support.justflight.com/support/solutions/folders/17000141909