Forum Replies Created
-
Posts
-
Yes, I think it’s about time that they support the users changing variables – allowing more careful integration with the various planes that we use. As the simulators expand their physics, we need the Brunner software to keep up.
As much as I love the A2A Comanche, I can’t really bring myself to fly it much. I just don’t have a “feel” for the plane. In general X-Plane seems to work much much better with Brunner, but it’s really noticeable in the Comanche.
Let me guess – this is the A2A Comanche for MSFS? I’ve had this problem there too, as well as the problem of not getting any datarefs from the engine/thrust to the rudder/yoke. This is due to the different system that AccuSim 2.0 uses.
The brakes is a different story, and I’ve tried solving it with A2A while in BETA, and we didn’t resolve it.
I’ve never had this problem with other planes in MSFS, however, so if this is related to other planes it’s probably a common source – which makes me happy. Easier to hunt down…
Yeah, this requires cooperation between A2A and Brunner. I heard from Scott Gentile at A2A that they have been in contact with Brunner and will get a unit to experiment with.
My take on this, given the fact that A2A has its own physics engine in Accusim running outside of the simulator, is that they need to send a “dud” of information to MSFS for the CLS2Sim software to read – a package of info to read, but not for the plane to act upon. This means that the Brunner software has the data to provide all the simulation that it does. However, this will only happen if this can be sent to MSFS without it messing up the physics of the lovely Accusim-plane(s).
An other option is for Brunner to supply an option inside of CLS2Sim for users to assign where the data comes from (and also what sort of “range” this data has, as I’m sure it’s standardized in the sim, which is why we must switch the software between MSFS and XP for example). This could be handy with many other planes too, btw, as other complex planes have different ways of controlling the engine physics and/or the control surfaces. The trouble with the AirfoilLabs planes was caused by them doing “stuff” outside the XP-standard, trying to improve upon it, but at the same time making it difficult to have Brunner hardware be compatible. This was recently solved by an option in CLS2Sim to ignore various axis.
The latter is more interesting to me, as I also have problems with the brakes on the A2A Comanche using my CLS Mk2 Rudder. Same problem, I guess – data coming from outside the regular MSFS datarefs.
It can be solved, I’m absolutely confident about this. It’s only a matter of all parties being open to trying some weird stuff to make it click into place.
I’ll help with any testing, whenever needed.
Yours,
Erik H. Aasland
I agree that things need to be updated to conform to platform changes, but not working in XP-12? I’ve been using my yoke and rudders since day… let’s say “day twelve”, as in the beginning I had some problems. After an early update, I had no more problems – though not perfect. I still get an error when connecting due to a “turbulence dataref” not being found or something. It still works as before, though.
After a recent update I get much much higher update rate – in the order of what was mentioned above here – 50-70. I’ve never had that before, and haven’t really felt that it was needed. As long as it has been stable and above, say, 15 or 20 it has been perfectly fine.
Again, I’d love to see more interaction and updates, but it is not a fact that it positively doesn’t work for everyone. I’m happily wobbling around in my DHC-2 Beaver, complete with all the force I need. 🙂
cdegroat82, I have the same issue. If you look in the CLS2Sim profile under effects, you might see that it doesn’t receive datarefs from the engine power. That’s why it doesn’t work. Probably an easy fix, but it needs fixing.
Apart from that I had no issues, and I had a 2 hour flight around with the new VSkyLabs Maule M7 today.
XP12 still has a ways to go in terms of bugs and compatibilities, but it’s very much on track. And the new weather system is to die for – it’s excellent!
Rolling back is simple if you have kept the previous installers. I didn’t, so I needed to get older software sent to me.
See this thread:
Both download and changelog is on this page:
Click on the button to load the content from http://www.brunner-innovation.swiss.
I had to previously roll back to a quite old version to avoid problems when X-Plane have too high FPS (who would have thought such a thing could happen?). I tried the new one, and those problems seem to be gone, but I had major issues with the rudders – they are rolling back and forth by themselves seemingly without provocation. I at least don’t understand what triggers them. Also I more often lost connection to my trim wheel after that update.
Back to the old software for now, until the Brunner-folks are back from vacation. 😉
Thanks, that would be fantastic! I usually try to keep around a few older versions too, but I’ve never had any problems so got complacent.
erik_bloodaxe_(A)hotmail.com
(A) = @ of course 😛
That is interesting, as the places I lose connection is in areas in XP where I get very high FPS…
Where do you find that old CSL software?
Hi,
I’ve started experiencing this too, lately. I have never experienced this before, ever since starting with Brunner yoke in 2017 and rudder in 2020.
Has anyone found any solution to this?
I’m running XP11.51 (or 52? Whatever the newest is), and firmware and software is updated. I have a feeling this happened after the last 602-608 firmware update, but I could be wrong.
It’s infuriating, however, as this constantly threatens my flying – especially close to the ground.
The 5 second reconnect time is useless for this. It needs to not lose connection in the first place.Hope the developers can be on the ball on this! @Sbrunner
Yours,
Erik
The problem for me was a conflict between the SimCoders software for the DHC-2 Beaver and the particular way Brunner uses datarefs. SimCoders worked out a solution for this, and it’s now working brilliantly.
A tip for that disconnecting in XP:
Go into the settings menu in CLS2Sim and check the “Auto connect” box little more than halfway down the settings page, in the middle. That way the software will autoconnect if you loose connection for whatever reason. I find that I loose connection when I enter the menu of X-Plane, so I make sure to not have to do that in the middle of a maneuver. 😛
I’m sure the holidays have been slowing things down, but I thought I’d just report back.
SimCoders have had a look at this issue and came up with a solution in their software, and the fluttering is now gone.
Read more about the exchange here, and do the simple fix if you also have this problem:
BTW: I tried using the Thrustmaster TPR pedals while this issue was resolved. They are fantastic pedals, but after using the Brunners for a few days before… oh well… no comparison. I thought force feedback rudders were unnecessary. I was wrong… 😀
You have probably already tried, but I’ll just make a quick post to say that I tried my Brunner Yoke in P3D v5 yesterday and it works just like v4, as far as I can tell… 🙂
