As I mentioned before I think he means the little glitch where it seems like some kind of polling hiccup between the A2A helper app and MSFS, which maybe would be on a regular pattern if you are near Main Thread limited in the scenario you are flying. I was getting it a bit - but not all the time. Happens more (only) when I was in heavier scene situation so it does seem like some CPU bottleneck to me.
I noticed also something that strengthened this theory for me. I have one specific place in the world now where my system literally dies. It is not due to my hardware because I can run fluid in New York or any of the other heavy hitter tests we know well for dense scenery / traffic etc that pushes the Hardware.
But for me, for some reason (yet to investigate with empty community) Cologne and around 50km radius around it is absolutely terrible. Unplayable.
I flew there with the 250 just to see what happened, and even when I get to the edge of this 50km radius where it smooths out normally, it was still hitching. Especially when I was doing some more extreme moves (was testing how it stalls / spins etc) so the ‘steps’ between physics frames were larger/more exaggerated per same timeframe as flying level. In that case, the plane was definitely kind of freezing (not a usual stutter) but where it didn’t know what to tell the plane to do until it caught up. If this happens when you are flying straight and level instead of already in a strange attitude that I was doing the spins, it results in a little ‘hop’ when the physics (or, well, the POSITION that the plane should have been in after the missed hiccup) is caught up with suddenly. Like it’s reacting to suddenly moving very quick to catch up the distance it would have covered during the missed frames. Similar to how a plane jumps when you teleport/spawn sometimes.
Dunno if that makes sense, but I think that is essentially what is happening. Feels like it needs a bit more optimisation on the helper app?
Oh god finally someone else! I reached out about it yesterday but I was the only one who’d had problems. You’ll find the yoke, pedals, doors, ailerons, rudders, hstab, dipstick the same, but not anything else.
Try raising the priority of the helper process? task manager is the easy way.
Correct me if I’m wrong, but isn’t a butt kicker just a speaker driver attached to a mechanical end (versus a speaker cone)?
If that’s the case, it’s just receiving audio from your normal speaker output and I’m sure it just has a crossover/low-pass filter that only cares about audio below a certain frequency. So there’s no coding in the sim that triggers it, just whatever audio is being sent. Perhaps the low-frequency audio from the Comanche is weak, or even compressed or high-passed. You’d have to run it through an audio spectrum analyzer to see where the lows are or aren’t.
Quick and dirty solution: run the audio through an EQ and bump the low end up. If you have the right gear, you can even do compression/expansion in a specific frequency band so it doesn’t get out of control when you use other aircraft.
To those of you who are using the Honeycomb Bravo:
Are you able to control the mixture in the cockpit with the Bravo mixture lever? It seems that I need a different control assignment but I’m not sure what because it works fine in other aircraft.
There are various things you can run that will auto set process priorities, but they all seem to cause other issues. I’m not sure if the helper app has any built in way ( msfs itself does I think ).
As I am on 7950X3D I wonder if it’s running on the same chiplet as the game. In which case just telling it to run on the other core would be ideal (if that would still be able to talk to MSFS). I’ll look into it. More fiddling!!!
I would think with that monster it’s probably MSFS choking that’s the problem rather than the helper… I have a 5800X3D, I’ll take a trip round Cologne & see how it is when I can.
After reading some comments here, I was very hesitant to buy this (non clickable cockpit switches, “some switches works weirdly”, sound interruptions or sound cut entirely, “non working AP”, “aircraft is beeping for no reason”, “you need to change bindings in some external app”, “it doesn’t feel even developed for MSFS”…).
But decided to open the wallet and have not found any big problems while using Honeycomb Throttle without any special configuration. Aircraft feels great and it is indeed very different to even the best GA planes in MSFS. The tablet and maintenance / diagnostic aspect is best you saw so far in MSFS, guaranteed.
I noticed only:
-After Gear Up with Honeycomb, light stays in UNSAFE and cannot be switched to OFF (obviously Honeycomb limitation as two position switch)
-Honeycomb Battery bind (via rocket switch) does not do seemingly anything, but needs to be switched on for GPS (GTN750) to work
-Honeycomb Generator/Alternator bind (via rocket switch) does not do anything.
So if anyone is hesitant like I was because of reasons above, go for it and read the manual to avoid surprises.
Is anyone else having trouble with manipulating the tablet in VR? In pancake mode I can grab and place the tablet with ease, but in VR I ‘lose grip’ easily which makes it a pain to place it where I want.
If you find a way to get it working with your Brunner, please let me know. Maybe something in the configuration will make it work?
I think that is the only remaining worry keeping me from buying this.
Yes, I flew it around last night in the hills east of where I live (Banning/Beaumont area of Southern California) and it was quite the ride with the Turbulence setting pegged to the max. I’m still learning how terrain affects turbulence, so it sounds like what I was seeing is very much in line with reality.
Just did my first test in this plane and WOW what an absolute beautiful frelling plane. Not a single hiccup or dropped frame. Worked flawless with zero tinkering and it even felt amazing on the gamepad. From takeoff to cruise and flying and landing the airplane felt real and so did my controls. Hide your wallets lol this one is the real deal.
Hats off to you fellas on this because the only thing I could find wrong with the plane was no metric toggle on the altimeter. Every other bit of info seems to be there. Otherwise a very robust and completely immersive package. If they could demo this product you would be buying it before you even land back at the airport haha.
Well done o7
PS If you are worried about external dependencies it does not install anything for startup in Windows just a small file that runs alongside the plane when you load it in the sim. It loads automatically so no worries. I was skeptical but alas I would highly recommend this plane.
I’m still in shock how good it is… breathe kwairt breathe lol
Yes buttkicker can respond to audio inputs from the sim but it also has its own software called Haptic Connect that responds to telemetry from the sim. That is what i usually use because it gives you more ways to adjust the various inputs. I will try using the audio input to see if that works for engine RPM.
It is so good, that ya hesitate to nitpick… but there is one issue worth mentioning… for me.
The engine modeling is crazy good. It’s so nice to see realistic relationships between all the goings on… makes making the effort to manage the engine realistically, rewarding and satisfying…
BUT
…there is a, thrust vs net power thing, at the low end of power settings. This shows up as being able initiate the tax roll too easily, and too high taxi speed per throttle position… and also shows up while trying to bleed of airspeed… on descent … particularly final/short-final…
The fix (and honestly this is no big deal… had to almost look for something to complain about), from my limited understanding; would be to do something like tune a curve between net engine power and thrust… so there is a little less thrust at lower power settings, without lowering higher power setting thrust… or mucking up the superbly modeled engine…something like that…
I’m still learning how terrain affects turbulence, so it sounds like what I was seeing is very much in line with reality.