Ranma13

I would just link to his GitHub repo where the 3D files are and skip all his BS: https://github.com/JonahTsai/F16 I'm Verisimilitude over at viperpits.org. The original thread was deleted, but basically he was ranting and raving about how he should get royalties for his 3D drawings if they're used commercially. Mr. Jonah Tsai conveniently left out my second and third follow-up post where I clarify further, but basically I pointed out that he cannot claim a copyright on a 3D drawing he made of an existing product and demand royalties from it, because all he's done is reverse engineer the original blueprint. He replied with a bunch of diatribe, but no sound reasoning at all. His whole argument rests on his erroneous belief that he should have a copyright because he created the drawings, just like how if someone made a clone of an existing product, they somehow have a right to sell it (or the rights to manufacture it). On top of that, shortly before deleting the thread, the admin of viperpits.org pointed out that Jonah received a lot of help from the community, who donated parts to him and gave him really detailed pictures to work off of. He credited none of these people and acted like he created them by himself, which really ticked off the admin and prompted him to delete the thread. That said, the admin did use his drawings to create a commercial ICP, which he sold a limited run of (20 units) on two websites and also eBay: https://www.realsimworld.dk/f-16-simulator-shop/center-system-parts/icp-intergrated-control-panel Whether this was a "dick move" or not is up to personal interpretation, but at least from a legal standpoint, since Jonah doesn't own the original copyright to the ICP design, anyone can sell one whether he likes it or not. And from a "this is how the world works" viewpoint, if he wanted to be paid royalties for commercial usage of his drawings, then he shouldn't have thrown it into a public repo accessible by anyone. This is like placing a sign on your front door that says "$100,000 inside, please do not rob me", then getting upset when you get robbed.

I tried it just now and there doesn't seem to be any issues with trim reset. On the right is my physical joystick position and on the left is the virtual position of the cyclic. When I trim away from the center point and reset the trim, the virtual position correctly jumps back to center, and all my joystick movements are once again relative to the center position:

All trim reset does is return the virtual joystick position back to the center so that your joystick movements will start back at the center point. It's useful if your trimmed virtual joystick position is somewhere off in the corner and you need to quickly bring it back to center. It's a "control" that doesn't exist in the real aircraft and is only useful for spring-based joysticks without FFB.

There's a large number of 3D modeled parts available here, including the ICP: https://github.com/JonahTsai/F16

Are you referring to the laser warning receiver? The Ka-50 doesn't have a radar warning receiver.

The MongoosT-50CM2 grip is "compatible" with the Warthog base, but not all the buttons will work unless the base specifically supports the grip. What sydost and I are asking is if this new FFB base is only compatible with the subset of buttons that are "TM Warthog compatible", or if it will support all the buttons on the T-50CM2. Based on your response though, it sounds like only the TM Warthog compatible buttons will work, but not all of them.

Does it only support the original Virpil MongoosT-50 stick, or also the MongoosT-50CM2 stick?

Swap axis only swaps the force feedback axes, his problem is that he's getting no FFB. Earlier you said that you were getting no center or FFB effects, but now you said that you're getting centering effect but no FFB. To confirm, is your stick centering properly, or does it just flop around with no resistance at all? Also, try the ForceTest app at the bottom of this page: http://www.fs-force.com/support.php If the stick doesn't respond to the FFB commands sent by that app, then the problem is with the stick. If it does, then the problem is somewhere within DCS.

Do you have the power cable connected on the FFB2? It needs both USB power and external power.

It's 40mm extruded aluminum.

You can differentiate USB 3.0 from 2.0 from the color of the ports, the vast majority of USB 3.0 hubs have blue-colored ports, whereas USB 2.0 is usually black or white. As for the Rift, it's best if you have it on a USB 3.0 port, but some quick searching online shows that there isn't a noticeable difference on USB 2.0:

Brunner rates it as 4.2 Nm peak force, they don't provide the nominal force. This one is rated at 2.94 Nm max torque and 2.35 Nm nominal. As Foxhoundcn stated, it's unknown if Brunner's value is the measured value at the stick, or if they're just going off the motor's specifications. Also, it's not "people", it's just one person, he's using a 12cm extension, and he doesn't say it's "too heavy". His exact quote was:

Yes, correct. With the AP channels off, the attitude hold and SAS are disabled, leaving only the force trim. The Flight Director button disables the attitude hold, but keeps the SAS and force trim enabled. Holding down the trim button keeps the SAS, but disables the attitude hold and force trim. If you have a non-FFB joystick, holding down the trim and enabling Flight Director will do the same thing. The difference is only apparent when you're using a FFB joystick. Edit: Added this table for clarity: --------------------------------------------------------- | Type | Force Trim | SAS | Attitude Hold | --------------------------------------------------------- | Trim button | | x | | | AP channels off | x | | | | Flight Director on | x | x | | ---------------------------------------------------------

No, it's modeled correctly. You're trying to fit your idea of how an auto-pilot should work into the Ka-50 and calling it wrong because it doesn't match your expectations. If by dampening force you mean what the West would call SAS, then holding the trim button doesn't remove it. The autopilot channels have two functions when they're enabled: the hold channel that tries to hold the attitude of the aircraft, and the SAS system. As long as the channels are on and not flashing, the SAS system is always enabled. Pressing trim only disables the attitude hold of the aircraft, but not the SAS. The only way to turn off the SAS is to turn off the channels. This isn't dangerous per se, it just makes the helicopter a bit harder to control.

All the FFB does for the helicopters in DCS is change the location of the centering force. When you press the trimmer, it will set the centering position to the location of the joystick at the time it's pressed: Most of the FFB effects in DCS are very simplistic, only adding a force trim effect but nothing else. Some aircraft like the Su-25T will go a step further and do things like make the FFB force stronger as airspeed increases and shake the stick if you're going too fast or entering a stall: And the TF-51D will occasionally jerk the stick to simulate wind, but as far as I know none of the modules do anything FFB-related to wind or auto-pilot.

M1Combat, you should stop basing your arguments off incorrect guesses. The AP does not move the stick on FFB devices. I think you should pick one up (MS FFB2 is only ~$50 on eBay), which will resolve your misunderstanding of how the FFB works. Sorry, I misspoke. To better clarify OP's issue, imagine that there's a rubber band around the front of the helicopter's nose, and every movement away from the rubber band will cause it to stretch and try to pull the nose back to the original position. When you trim, you're resetting the rubber band's position to wherever the nose is pointed at the time the trimmer is pressed: When you hold down the trimmer, this reset is happening constantly until you release the trimmer: OP's issue is that he's moving the nose to a position that he wants, but some of the movement he's applying is to counter-act the AP pulling the nose back to the original position. He gets it stable, but when he taps the trim, the rubber band effect suddenly disappears and the helicopter jumps more than he intended:

Very compelling argument. How can someone argue with "no"? Oh wait, I know: Yes.

It doesn't have to do with central trimming mode, all that does is make it so that whenever you press trim, your joystick movements will be ignored until you return the joystick to the center position. The reason why it jumps is because people are using non-FFB joysticks where they hold down the trimmer instead of tapping it. The same jumping effect can be observed if you've trimmed the helicopter, then turn on Flight Director without touching the joystick. Flight Director does the same thing as holding down the trim button, except it doesn't disengage force trim effect.

Depending on how many devices you plan to plug in, you may not need an A/C adapter for the hub. Contrary to popular belief, bad things won't happen if it draws too much power; the motherboard just won't provide enough power and the USB devices won't behave properly, but that's about it. With just a throttle, joystick, and TrackIR plugged in, I think you're safe without an A/C adapter, but I suggest getting one with an adapter just in case. Stick with USB 2.0 hubs, they're cheaper and you don't need the extra bandwidth USB 3.0 provides. You might also want to get one with more ports; you never know if you'll buy more accessories in the future. I have this USB hub: https://www.amazon.com/gp/product/B00HL7Z46K/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 And I'm already using 11 of the 13 ports. It also has 2 buttons on it to enable/disable the ports, which is great for saving electricity and for when you play other games that picks up your joystick/throttle as input devices, causing unwanted movements like spinning the camera around or moving your character.

I agree with csdigitaldesign, auto hover is fine. The Ka-50 was designed so that you're either employing weapons in a stationary hover or you're flying around, but not doing both at the same time (unless you're doing a rocket run). If you feel like you have to move around in order to stay alive longer, you're too close to the target.

Real pilots tap the trimmer. Holding it down removes the force trim effect on the stick, which makes it flop around and is undesirable. The clicking sound is not the trim button itself, but the magnetic brake disengaging and engaging.

Unfortunately I haven't been able to find a workaround. The problem is that DCS treats the game as one render surface that it renders viewports into. If even 1 pixel spills into a lower refresh rate monitor, the FPS will be capped to that monitor's FPS. The fix would be to treat viewports as separate windows, but I doubt it will ever be implemented.

In real life, the rotor blades will give the helicopter away. In DCS, this isn't modeled, so only the body of the helicopter is taken into account. If you're flying low and slow, there's a good chance you'll escape detection, both because you're a smaller target and because people in jets usually don't slew their radars that low. However, in multiplayer you're getting found because of AWACS and the datalink. You've probably noticed that nearly every MP map will be along the coast, so although you can hide from AWACS by ducking into a valley, that's really hard to do along the coast.

To elaborate on this, the speed shown on the HUD is the ground speed from the doppler nav system, which is powered by the INU switch on the back right panel. It has a startup time of around 3 minutes. The speed shown on the Shkval is the indicated air speed and it matches the analog gauge reading. Below 50km/h, it will show 0 due to not enough ram air entering the pitot tube to get a reading. The ABRIS shows ground speed measured by GLONASS. This is why the 3 "speeds" that you see in the cockpit often won't match up, because they have different sources.

It's the price. People are losing their minds over the $230 TM F/A-18 stick, a $500 stick is not even within their realm of comprehension, no matter what kind of features it has.