Hiob

Keine Panik. Ich hab‘ ne 4090 und der Rechner zieht in DCS nie mehr als 500W aus der Dose (wohlgemerkt der gesamte Rechner). In RTX Games wie Cyberpunk 2077 vielleicht mal 600….. Die nominellen Höchstwerte, wenn sie denn überhaupt erreicht werden, treten in der Regel ja nicht simultan auf. Und Dein Netzteil wird auch nicht gleich in Flammen aufgehen wenn es mal 90% liefern muss. Und Be Quiet Netzteile sind kein Ramsch, die liefern auch ihre Nennwerte klaglos. Schlimmstenfalls schalten sie ab.

That seem a bit low to me. Even for a efficient CPU like this one. You are positively running MT? How is the FPS limiter in DCS set? In the past setting it to 300 introduced problems with fps and frametimes. Don’t know if that is still a thing. Generally it is advisable to use external limiters like the driver or RivaTuner Edit: Obviously I‘m just shooting in the blue here. Just some variables that have caused issues for me in the past. Edit2 Since I‘m already brainstorming - are you using some kind of monitoring software (like HWinfo), RGB-software like iCue or Logitech….. or something like Aquasuite? Try it without those in case. Last but not least, just for testing, turn off the power service.

Kommt ein bisschen darauf an, wie Du DCS spielst. Angenommen Du spielst hauptsächlich Single Player und weniger komplexe (vielleicht selbsterstellte) Missionen mit einer überschaubaren Anzahl an Einheiten - auf jeden Fall die GPU! (btw…. hab eine 3080 abzugeben….) Wenn Du schwer gescriptete Kampagnen oder aufwendige Missionen und oder Multiplayer spielst. Oder in VR, ist es vielleicht sinnvoller, die Grafik settings ein wenig zu reduzieren (wenn nötig) und in einen schnelleren Prozessor zu investieren. Wenn Du den detaillierten ingame frametime Grafen aktivierst, kannst Du sehen, ob Du überwiegend CPU oder GPU limitiert bist. Deaktiviere aber vorher alle fps limiter (oder setzte sie auf z.b. 180) falls Du welche gesetzt hast.

CPU temps? under load?

Well, if the ball in centered you fly in aerodynamic trim. It tells you all you need to know. However there is very little penalty (apart from fuel efficiency and speed) for being a little out of trim or flying in a "nose-tail" trim.

Push, würde die Sachen auch einzeln abgeben. Außerdem wären noch im Angebot eine - VKB Gunfighter III Joystick base (ca. 1 Jahr genutzt, funktioniert einwandfrei) sowie - VKB F-14 Tomcat Replica Grip. (Neuwertig) Bei Interesse PM

What kind of RAM are you driving? (Amount, number of sticks, speed?) ah, sorry. Just saw it in your original post. Do you have some kind of failsafe defaults you can load in your bios. Deactivate the XMP on the RAM and try from there.

Hey, thank you for engaging with this. No. I‘m not using the launcher. FFB is enabled. I changed no settings inside DCS. I know that trimming does nothing on the ground. but when speed builds up and you need to increasingly trim nose down, the stick should follow (which it did), which it now doesn’t anymore. I‘m completely aware that I might messed up something on my end, but I can’t figure out what. Do you want me to record a track?

EDIT: The issue was solved! It wasn’t the Phantoms fault at all. The FFB device had a hickup, that was either solved by a firmware update and/or an USB power cycle. Sorry for the alarm! Hey, usually when I trim the F-4 the FFB Stick would follow. So if trim nose down for fast cruise, the sticks center position (or force free position) would move forward (quite a bit). However, that doesn’t work anymore. I can see that the trim hat inputs are registered and the bob weight indicator in the controls overlay is moving forward - but the stick doesn’t follow. I did any troubleshooting on the FFB side of things I could think of (including deleting and re-enabling the export.lua) and every other FFB aspects seems to work. Any ideas? Thanks in advance!

Prinzip bedingt gibt es eigentlich keine Deadzone. Lediglich die Feder/Rückstellkraft wird halt sehr niedrig. Beim Rhino kann man dem via Software begegnen, indem man die Kraftkurve entsprechend anpasst. Ob die Software beim Moza auch schon soweit ist, weiß ich nicht.

Well, the sweet spot in the Q3 basically goes from edge to edge. Thats a big plus. I would invest in a more comfortable headstrap that sports an extra (swappable) battery. (~100 bucks) I never had a G2. But coming from the Index, the Quest 3 is the far superior experience. I might add, that I also invested in a Wifi 6E router to take full advantage of virtual desktop. But even with those additional expenses the Quest 3 was still much more affordable than the Index. One of the biggest selling points to me was the passthrough. A big game changer for me above the Index to actually using it for DCS. Oh, and the inside out tracking works great. Another BIG plus above the Index with its damned lighthouses.

Update Bios Update chipset drivers But that‘s actually the reason I‘m still using my 5900X instead of a 5800X3D. The former runs buttery smooth, the latter I couldn’t figure out why it caused a lot of (micro-) stuttering. I‘m sure there is a reason and it can be fixed, but I haven’t found it unfortunately.

Yes. Walmis sells the motors and logic board that work with the Rhino software as Kits (VPforce.eu) and there are DIY projects for all kinds of devices based in them. I made a mounting solution for the Crosswinds. @kaltokri is selling Kits based on my design, but you can also go to the project page in the VP discord and find the files and instructions for 3D printing and building it on your own.

You should. It‘s easy and a perfect complement to the Rhino stick. (A considerable investment still, can’t argue around this)

Now you need to upgrade your Crosswinds to FFB with the Rhino mod as well!

Ich denke nicht, dass es an DCS oder der Quest 3 liegt. Von Deinen Specs solltest Du auch in der Lage sein mit halbwegs vernünftigen Grafikeinstellungen überwiegend flüssig zu spielen. Ich kann leider nicht 1 zu 1 helfen, da ich die Quest 3 mit Virtual Desktop über WiFi betreibe, aber QuestLink hat prinzipiell auch funktioniert. Ich würde mal testweise den Game Optimizer deaktivieren (oder deinstallieren) - vielleicht funzt der einfach nicht mit DCS?

Hey, der "kommerzielle" bzw. offizielle Rhino wird nach wie vor produziert und angeboten. Wegen Details oder bei Interesse schaust Du am besten mal auf Walmis' Website (Vpforce.eu). Dort gibt es auch einen Link zum Discord. Da gibt es die besten Infos und Hilfe zu dem Thema. Was Du im Kopf hast, ist wahrscheinlich Winger, der die DIY-Kits für den Rhino angeboten hat und das jetzt nicht mehr macht bzw. abgegeben hat an Kaltokri. Falls DIY etwas für Dich ist, wäre das eine gute Option schneller (aber nicht zwingend günstiger) an einen Rhino zu kommen. Der Moza ist definitiv das "kommerziellere" Produkt. Meiner persönlichen und subjektiven Meinung nach aber nicht besser als der Rhino. Dessen größte Stärke ist die Software und der Support. Da wird Moza so schnell nicht 'rankommen.

Fairer Weise muss man sagen, dass er den Rhino bis Weihnachten nicht bekommen würde. Höchstens als Bausatz. Ansonsten würde ich voll zustimmen!

First of all, your logic game is weak. Making a statement about a group doesn't necessarily imply a statement about a different or opposite group. Apart from that you conveniently left out the relativisations I made, like "most" and "unlikely". The judgement that most unbiased people most likely won't buy more than one expensive FFB-Joystick simply stems from the reasonable assumption that in general most people probably won't buy two different ones (at the same time.) The term "unbiased" was simply put in to emphasise that I don't care about the chills that got free review samples and want to boost their click rates on youtube. Seriously, how is that hard to understand?

That’s not what I said.

I think, from the existing reports, it is save to say it will do better than the Brunner. We just don’t know yet how much better (and how exactly it compares to the Rhino). Unfortunately most unbiased people most likely won’t buy two units just for the fun of fueling forum discussions

I‘m running DCS stand alone. All I can say is that after I launched it from the actual virtual desktop it then appeared in the virtual desktop app games menu the next time. Worked either way though. Btw. make sure you try hand passthrough with the Quest and VD. It is awesome! The passthrough options alone make it soooo much better than my old Index (apart from the ease of use and visual clarity!)

Btw. does the Moza report temps in the first place?

Simply use an aircraft (like the F-16) that can hold high Gs for a prolonged time and continuously fly two circles. I mean the physics is pretty simple. Make the stick apply maximum amps continuously and see how fast it heats up. Since the max torque is supposed to be the same, the amp should be comparable too between the sticks. Note that the temperature reported (most likely) is that of the motor driver, not of the actual coils or magnets. As long as the thermal mass of the motor is not saturated, they will work as a heat sink in the rhino. So it cools down rather quickly after a dogfight. You only get into critical thermal regimes when you do that over and over again until all the thermal mass/heatsink of the motors is saturated and can’t be cooled down efficiently anymore. I only managed to do that by deliberately trying to find the limits. I assume the Moza will behave similarly. If the case as a heatsink is more or less effective than actual ventilation….. dunno. Kind of doubt it. Well at least they connected the more loaded motor to the case.

The first video isn’t showing anymore. What was it?