Berniyh

That is true. The good thing however is that the Brunner is so precise that you don't really need an extension to fly choppers. Or at least I don't. :) Of course it's less realistic to do it without extension, but it's doable.

Without an extension the torque will definitely be enough, don't worry. And the whole extension thing really depends on the parameters. Even Brunner highly disrecommend using an extension because of the troubles that such a setup can bring. Ultimately it depends on the specific setup if it makes sense or not.

Brunner have beta support for DCS now, but I think they implemented it with a plugin rather than HID FFB.

Depends on what you want from it. It'll work with an extension, but if you put a heavy grip on top of it (like the Warthog) using a long extension (+10cm) it won't be able to hold the grip almost certainly. Even the Brunner, which has almost twice the torque, has issues with extended grip setups.

@kingpinda: thanks for the info. I'm not in a super rush to try it out, but it's good to know that there is now at least experimental support. :)

At least with the unmodified base, the analogue brake worked as a button. They might have changed that, but I wouldn't bet on it.

ok thanks, so they don't fit either. Even with the tight layout, the width is at least 454mm and I have only 435mm available. So I keep the VKB pedals. ;)

Can anyone tell me the dimension of the pedals (either version)? Both in the middle position and when pushing either way (some pedals change width in that case). Couldn't find that info in the shop (although IMO it should be there). Asking, since I've got only a limited width in my rig.

Actually there are quite a few sims that can do it. And the separation is usually graphics/main, physics, AI and maybe audio (so that'd be 4 threads, but possibly more if you split AI and physics onto multiple cores each). On the commercial versions of the sims they often offload the physics calculation to a second computer even. No idea though how it's done on DCS.

Since Windows 7 is nearing an end, I wanted to give DCS under Linux a try again. I actually got it to start using Steam (I'm not using the stand-alone version), proton, protontricks and winetricks. He're is what I did: 1. Install DCS using steam (obviously), first without any DLCs (to exclude activation problems) 2. Add vcrun2015 and corefonts: protontricks 223750 vcrun2015 protontricks 223750 corefonts3. Run it, it starts up in windowed mode. No it's far from running perfectly, but at least it started. That's progression, I'd say. :) There are rendering issues. MXAA doesn't work (gives you weird coloring) and even without, it looks very strange. Performance was horrible, but I think it would be better if using DXVK. After that, I added the Huey DLC to see if activation also works and indeed it does. So there is hope for us Linux users that at some point it'll actually work. :thumbup: (Obviously a proper port would be even better, but that'd be a long way to go. A very very long way.) Edit: I tried with an updated version of radv and now DXVK/radv works. Visual glitches are gone as well. Performance in high profile is ok, 35-40 fps with my RX Vega 64, but a bit worse than on Windows 7. Arount 60 fps in Medium profile. Joysticks work as well. So … good progress. :)

He thought it was a great idea until he pushed the stick forward and the rotor cut his head off. :P Seriously, interesting design. :D

Jep. Just as you would expect in a helicopter and some aircrafts. Last thing we heard about this is a quote from someone working at Brunner that due to the increased interest from DCS users, they start (or started?) working DCS support. Not sure if via a plugin (meaning generated FFB) or DirectInput FFB support (so it work in pretty much any software supporting that). I suspect the former.

Pretty certain it's a direct connection to the servos. You can feel the grind of those when you move the stick.

That is Navi and it's supposed to replace Polaris (the RX 5xx). ;)

Navi is not a high-end GPU. It might reach Vega 56 or maybe Vega 64 level, but most likely not higher.

Can't say anything about specific parameters, since I can't launch the gaming PC right now, but regarding the oscillation: that's nothing to worry about, it happens in a lot of feedback devices. Basically it's due to a feedback loop similar to what happens when you place a microphone in front of a speaker which outputs the input of the microphone. In that case, noise gets amplified and suddenly you hear loud noises. The same happens with the ffb stick, due to the centering force, it's start to oscillate due to small fluctuations in the controlling signal. It can be prevented by applying some damping (can't remember right now if that is available in the software, but should be) on both axis, preventing the amplification of the effects. You will also not feel the fluctuations when you put your hand on the stick, because your hand will act as a damper as well, preventing the amplification of the fluctuations. Note though that damping will also result in a less 'crisp' feeling of the FFB (in case you're playing a game for which an FFB plugin exists). So don't apply too much damping.

Of course not, but also not worth the ~20-30€ you save when getting an additional 8 GB instead of 16 GB. (in addition to a 16 GB kit already installed) Prices depend highly on clock speed obviously. Approximate prices are: 8GB: 35€ (2400 MHz) - 60€ (3200 MHz) 16GB: 65€ (2400 MHz) - 80€ (3200 MHz) 32GB: 130€ (2400 MHz) - 160€ (3200 MHz)

24GB means you're mixing RAM modules. That can work, you might be able to get dual channel working with that, but it's risky. The system might also run in single channel only, which would mean a significant performance hit.

Looking at your memory usage and saying "doesn't use 100%, so more is not needed" is a bad test. That is, because an application or game on startup might check for how much memory is available and then decide on a memory usage strategy to best make use of the available resources. So doing the same test on 32 GB might show much higher memory usage, if they implemented it that way. However that does of course not mean that more than 16 GB will improve things, but rather that different tests are needed. Best test would be to run it on a 4×8 GB system in dual channel and then compare that to the same system with 2 of the modules removed (also in dual channel). Personally, for a new system, I'd recommend 32 GB, even if DCS doesn't fully benefit from it right now. Thing is that memory consumption will only go up, so in the future you might benefit more. So it's more future-proof. Also, right now memory isn't that expensive any more. Upgrading an existing system that has 16 GB on the other hand wouldn't be worth it.

They are possibly out of ideas as well. (without a device at hands) Edit: even though it's not their job, it might be worth contacting Virpil support as well, maybe they've got a suggestion how to fix this. Maybe you have to just short-circuit two pins or something like that.

Yeah, because that is what makes sense according to the Virpil product page (Warthog/Cougar compatibility minus some buttons). tbh, I doubt a software update would help here, this should work without, because there most certainly is no software update for the Warthog base either and the electrical wiring between the two bases shouldn't be that different. But fingers crossed that they come along with something that actually helps. btw, you don't have by chance a Warthog base lying around that you could try the stick with, just to see if it works there? And there is no magical switch on the grip for a compatibility mode?

First congrats for receiving your base. I hope you'll get it working and have lots of fun with it. :) But it's indeed very sad that it doesn't work with your grip. Have to say though that this confuses me a bit, are the two Mongoos grips not compatible to each other? It's actually said to be compatible with the Warthog base and in that case it should also be compatible with the Brunner base. However, there is an annotation on the product page that not all buttons will work on the Warthog base, so I guess it's the same on the Brunner base (which was mainly designed for Warthog compatibility, it seems). Unfortunately, it doesn't say which buttons are affected. btw, I already asked Brunner about whether or not the analogue brake lever could work and they told me that they cannot do that and it will only work as a button.

Sorry, I don't do Youtube. Personally, I've got a aluminum profile rig mainly for racing (I also own a Simucube steering wheel). So for me the logical solution was to get the Monstertech mounting frame for the Brunner stick: https://www.monstertech.de/en/product/joystick-throttle-mounting-plate/ And then fix that to the rig using profiles. Of course, if you've just got a desk or chair to mount it to, then that might not really help. But for those cases they have some clever stuff on their side as well, no idea if those are worth it though.

ok checked it and it is possible. You have 4 commands for this: Trim - evelator up/down Trim - aileron left/right You can map these to any button on the joystick and when pressed (and no external force is applied) the joystick will move to forward/backward/left/right depending on the button, due to the trimming force. You can also set the trim velocity, which in this case defines the size of the steps each button push will induce. (or if you continuously press the button, how long you have to press it for a certain movement) In case you have their rudder pedals and/or collective, you can trim those as well, but I doubt that anybody does, the stick on its own is expensive enough. ;)

ah ok, I see. So basically you're looking for a way to incrementally move the force center position with 4 buttons, right? So far I didn't look for something like that, so I'm not sure if that is possible, will need to check. I'll report on my finding later today after work.