adam12

Good to know

The more I get to know this the less I think it should be called a trim system at all. I know that it works to the same end as the trimmer on a fixed wing aircraft, but just from a psychological standpoint to avoid confusion it would be better if the comparison was never even made. But I get it finally :) I'm not sure how the collective / altitude hold works. Press collective brake (F by default) to set altitude but what does this do between the collective in-game and your flight stick? I notice I still have full control over power. Is it a 20% limit? I don't see anything on the mechanics of the thing in the manual but I swear I gave it a good check.

Haven't looked at the tracks yet but sounds interesting. (How do you know when they are killed? I notice always some delay after the rounds hit before the vehicle shows any animation of explosion.) I'm not sure why this is but maybe we could find something on the net that would explain. My instincts tell me that's not a bug but it doesn't line up with what I understand about real 30mm HE. It appears AP is going through but not damaging the vehicle, but then why are some vehicles able to be killed with HE and not AP? (That must be a bug?) Very strange! Is the AP round a sabot type? Next time I get a chance to play I'll shoot some AP at different ranges at the targets you couldn't kill and post the results, if you don't get to it first.

That all sounds reasonable, I'm pretty happy with it.

My belief is that HE rounds are only in the TOE for killing infantry and destroying their cover (bunker/building). AP much better imo. Some very soft targets (trucks with canvas roofs) would be hurt by shrapnel just as much as a direct hit. Improved trucks are protected from shrapnel so a direct hit is required for both HE and AP. AP will destroy whatever it penetrates and penetrates more than HE. HE will not always destroy what it penetrates. There is an argument against single shot AP in that it can go through some APCs and not hit anything critical. Burst fire resolves that. No qualms with HE, like I said, I just think AP is the better choice.

I'll test some more, but just let me state the argument: I didn't say HE couldn't kill anything. So let's put that aside. What matters more to me is that I can use AP to kill any vehicle HE can kill. Yes, HE can disable a tank that you can't kill. That's what your Vikhr are for (killing tanks). AP will damage tanks too btw. Some points on realism -- HE is an infantry killer. That's really why it's on the helicopter, not for peppering Abrams from the frontal arc to disable systems. Infantry in DCS are not modeled adequately (and that's fine!) for them to be anything but shooting gallery targets in the sim. And they can be killed by AP too. ---

Just load all AP. HE is useless in this sim. It's for shooting infantry. Unless you want to pretend there are troops in buildings or you want to go around sniping singleton infantry that just stand there and have no way to hide from you.... The only possible application I can see where it might be useful would be a proximity fuzed HE round for use against helicopters. DNE.

Impossible to know without the track, but could you be experiencing an electrical problem? Maybe too much drain?

Nevertheless very interesting to learn about. Thanks for the feedback.

Can I have a review copy? :P

Somebody should tell CCP about this concept.

The file is now available. Turn on time compression until you see the rotor brake being disengaged.

I'm curious what you guys think of the statement bolded. It's not something I've been able to cross-reference anywhere else (yet)

Cool, through this I also learned that the autopilot isn't just a damper system. Good catch!

There is a second force feedback option, under trimmer forces. That's what I'm talking about. And when you use this bloody joystick, anything can happen. :)

I didn't realize the FF even worked with this game. I had so many problems with oscillations (the joystick is really a hunk of crap in terms of quality) that I looked up on the net about the stick and was told to disengage FF entirely. Something about the Logi Profiler doubling the FF. I'm glad I turned it back on again. Things are working fine, I just don't use the stick shake. On to the autopilot :smartass:

From overhead I'd expect the RCS to be much larger, as well as underneath. What about for ground based radars operating at roughly the same height? I'm imagining the physical area of the blade, looking at it edge-on. But, I have no idea if the *size* of a moving object has any affect on the doppler return.

What I meant is natural airflow up the hills. It's something I read here: http://helenkrasner.suite101.com/vortex-ring-state-a51416 "The approach to off-airfield confined areas is another situation where vortex ring can easily occur. Again, there is often a high workload, the airspeed is likely to be low, and the pilot may have to approach downwind or not even be sure of the wind direction. There are a few less common times when vortex ring can occur; according to an experienced mountain pilot, up-flowing air in the hills can give the same situation as being in a descent. It should also be noted that conditions for vortex ring can differ depending on weight, density altitude, and helicopter type. It can also occur occasionally without warning. It is therefore something of which helicopter pilots should always be aware."

He's right that the RCS of blades on doppler is quite small though, regardless, isn't he?

I'll have some time to fiddle with it tonight, but for now just want to say that there IS a completely valid reason to hold the trim button down while you position. It disengages the dampers. Since I've not even touched the AP/Damper system yet (having not mastered trimming) I haven't yet used that method, but in those situations it's the only way to go, save disengaging the AP and then flicking it back on again. (more work.)

I think I know what is going on... My joystick is a Logitech Force3d. It sucks, horribly. Consequently, all forcefeedback in the game settings are set to zero, including trimmer force. (Even with it turned on, the joystick doesn't respond at all with force feedback. This is a universal problem with this stick.) I think BS is reading my joystick driver and noticing it's a forcefeedback stick, and automatically implementing the forcefeedback method of trim which holds your joystick in position with the motor gears in the stick. Alright, so how do I tell Blackshark that this *isn't* a forcefeedback stick (as is.)

Does the sim model mountain effects on RVRS?

I have uploaded a demonstration of the problem. Once the file is checked out you will be able to download it at http://files.digitalcombatsimulator.com/en/110089/ The file is now available.

I have noticed several times where I am caught in a descent that I can never break out of. Adding power doesn't help. I think the blades are stalling out, and if you don't have enough altitude for some "zero pitch" time (to build up blade speed) you're in a situation you can't get out of. Eject.

Currently being "checked" but here is the link http://files.digitalcombatsimulator.com/en/110088/ Bear with me at the start, it took me a couple minutes to realize I had the rotor brake on ><