Socket7

Op says he's only asking questions, but is doing so by quite blatantly demonstrating his awareness that something is not right. Reminds me of when you ask a child if they ate a slice of cake and they think you won't notice frosting smeared on their face. For the amount of effort that was expended by OP on this endeavour, a useful bug report could have been created instead. :dunno:

In the very early days of DRM, when it was a lot easier for programmers to screw with critical parts of the windows OS, DRM devs thought it would be clever to piggyback their crap on critical parts of the infrastructure. For example, inserting itself into the windows TCP/IP stack. Then the user uninstalls the game, the DRM is buggy and doesn't restore the TCP/IP stack, and you have no more internet, and it's nearly impossible to fix without a format. I remember a specific DRM issue like this. I know there were others as well. The public didn't like this much. Microsoft didn't either, because their OS got flack too. DRM doesn't do that anymore. It's against policy, and microsoft doesn't let them get their meathooks in there anyway. In fact, the last time I remember hearing about a game destroying a bunch of computers, it was EVE Online, because they typoed a line of their installer. and installed the games boot.ini to C:\ (Why they used boot.ini as a config file, the world will never know.)

The most soul crushing part of DRM for me is the the sheer volume of serial numbers I have to enter because I own so many modules. I don't think I've ever uninstalled a single module correctly. I've been through 2 computers and 2 OS formats on each and they all still have 6 activations left... I'm not worried. :music_whistling:

No controls indicator shown on a video saying the controls are not touched. Not that I think you touched them, but a little thoroughness is in order if you are going to make this thread yet again.

Magnetic trim just sets the center point of your cyclic axis. If you deflect your cyclic 50% forward and hit the magnetic trim button, your cyclic will center at that 50% forward deflection. In a real helicopter, the cyclic stick would move forward halfway and then be held there by the magnetic trim system. You can "center" the cyclic at any place you please. For us simmers, there is no way to make a joystick center anywhere other than it's center, So when we use the magnetic trim, we have to re-center the joystick, while an actual pilot does no such thing, because his cyclic stick does not have the same limitation. With the fine trim, you can only adjust your cyclic by a few degrees (I believe you can see how little by watching the controls indicator, but I could be wrong). It might be enough for flying in still air on a clear day, but if you add in a bit of wind and turbulence, you'll suddenly find the fine trim to be quite lacking. The designers of the helicopter gave you both trim systems for a reason, It was not so that you could completely ignore one. Use them together, as they both have advantages and shortcomings. :thumbup:

You guys realize that the hat trim has a limited range, right? It only goes so far. Magnetic trim lets you set trim your cyclic to anywhere at all. You should set your rough trim with the magnetic brake, then fine tune your trim with the fine hat trim.

Yes. You should be using magnetic trim. Everyone should. It works like the other helicopter trim systems. Get flying the way you want, press and release the button, then re-center your joystick. Once you use magnetic trim to get yourself close to how you want to be flying, use fine trim to get it just right.

base made of some box tubing and some standardized mounting rail. Pedal shafts look suspiciously like a wrench. (edit: someone else nailed it, they are bicycle pedals. ) I really do envy how easily the chinese get a hold of raw parts. I don't know where I'd get those end cap joints that connect the pedals to the hall sensor in the middle. Probably works better than CH pedals, but not by much. Gonna have a nasty center spot like the CH do they have the same tension design.

As you raise the nose to slow your forward speed, you have to lower the collective to avoid climbing. As your forward speed reduces, you begin to lose translational lift and you then need to reapply collective to maintain altitude. If you anticipate needing that extra collective because of the loss of translational lift, and add it before you being sinking, your transitions will get a lot smoother and you'll be less prone to getting into VRS during them. Keep a note of how much collective you need to hover while stationary, and you'll begin to get a feel for how much you need to give it to slow to a perfect hover from forward flight.. It will all become natural instinct once it "clicks". For landings try and get as low as possible before entering a hover. Descending 100 meters in a hover leaves you in a precarious situation for a very long time, making you impatient, making you rush things and crash. (Or at least, that's what always happens to me.) If you want to practice hovering, try sling loading cargo. It demands precise hover control. I made a mission for landing practice in the MI-8, actually. When you can beat this mission reliably, you'll be an expert! Or at least competent. :pilotfly: http://www.digitalcombatsimulator.com/en/files/1277734/ Uhm. Let me know if the latest version of DCS has broken anything in it. I dont think it should have.

See my previous reply in the other thread just posted today about SLI... SLI absolutely works in 2.0.2. Some games simply won't use both cards, and when you try and force it to run in AFR the game will crash. This is not so much a "problem" as forcing something that isn't supported and causing a game to crash. When you leave your nvidia profile settings at their defaults, SLI will not cause crashes or instability. It just might not use both cards. http://forums.eagle.ru/showpost.php?p=2853213&postcount=6

yup. Nugget is a normal term for a pilot in training. Battlestar Galactica calls their rookie pilots nuggets too. I'm sure there are other examples in pop culture, but that's the one that sprang to mind.

you should be able to see the amount of time until your DHCP lease expires too. I'm not sure how to check that information on the router itself. Dig around in the DHCP or network information settings. In windows, you can do an ipconfig /all and get the lease creation and expiration date, but that wont help in this case because it will only tell you how long your desktop has its 192.168.1.x lease to the router, instead of your routers lease on an internet facing IP.

SLI works in 2.0.2 natively in surround mode, no tweaking required. SLI works in 2.0.2 in single monitor SLI mode with AFR forced on in the nvidia control panel. you gain about 20-30% improvement. There are absolutely gains to be made. 1.x is much more CPU bound, and since I'm so bored of the caucus map, I've not done any testing with it. I run x2 4gb GTX980's Haswell-E at 3.7ghz. X99 chipset 16GB of DDR4 I am not CPU bound in any way in 2.0.2 Not a single core hits max. However, even on the lowest settings, I cannot manage 60 fps at 5760x1200, due to Vram and GPU power constraints. If you come back down to 1920x1200, instead of triple monitors, things get much better, but I still cannot max out all settings. So basically, SLI works, It has gains, but it's a fools errand to think it will allow you to use 2 cheap cards to equal one expensive one. If you don't have 8 GB of Vram, your FPS will tank on high detail settings, period. I verify CPU, RAM, and GPU usage with HWinfo64, which will give you real time charts of all those things.

The new caucus map has breakers on the beaches! It's so nice to see an update for it. the map really was beginning to show its age, especially in contrast with nevada.

Fan and a cupholder please. A fan alone would be good, but if I didn't have to hold my FatDonalds cup while flying it'd really make the MI-8 guys look like chumps. :lol: One caveat though. I don't want the copilot being able to sip my drink or put his cell phone in my cupholder because "The cord for the radio aux jack isn't long enough to put it anywhere else." That'll only take like, a day, right? :megalol: Waiting eagerly but patiently for the latest update!

A beautifully detailed and rendered airplane does not a flight model make. I would imagine a lot of the data you would need to make an F-35 fly correctly in DCS would be classified. Things like turning and climb rates and max G-loads are also the kind of things it's handy to know if you want to shoot one down in the real world, and the sort of things lockmart and the US government wouldn't want widely known for as long as humanly possible. Perhaps DCS is just not capable of handling the number of times you need to 3 finger salute the radar system during a flight. :lol:

#1: Try alt+enter to switch to fullscreen mode. #2: Your resolution is set to 3840x2160, which I assume is from DSR? Lowering it to the native resolution of your monitor should also resolve the issue.

having FFB racing wheels plugged in while playing DCS has broken trim for aaaages. I remember running into it at least a year ago when I was playing Assetto Corsa frequently. Unplug the wheel, trim works again. Nice to see a fix is finally in the works.

I would hope that buttons that cannot be rotated, because you're supposed to push them. :P Wordplay aside, it seems pretty logical that both players should have access to switches, knobs and cup holders in the center console, where only a single player can reach switches that the other player would not physically be able to reach in real life. (Unless he leaves his seat, A pilot has no way to physically reach the dust screen switches on the MI-8 or program a new course into the doppler system. for example.) If only writing code was as easy as "well, it's logical for it to work that way." :)

You get a new IP every day? How annoying. I like the idea others have had to talk to your ISP about getting it to happen at a different time. I had to argue with 2 techs and a supervisor just to get a DHCP release and renew so that my new router would work with FIOS. IP's don't change for months and months at a time. How would the server know that the new IP is the same user from the old IP that got disconnected? Some kind of authentication token?

I love the way the MI-8 enters VRS. After many hours flying it you can actually feel it start to flounder and claw at the air right before it begins plummeting to the ground beyond the hope of any additional collective pulling you out of it. Aside from a lot of practice, the best way to avoid VRS is not descending while below ETL. Keep yourself moving forward and practice flaring to a stop and hover just above your landing spot rather than flying over, hovering, and descending.

Yup. The 1.5.4 version does not have this bug. Ran through the cold start tutorial on 1.5.4 and could not get it to misbehave. So it's already fixed, we just have to wait until the next 2.0 update for it to get over to nevada. At least i know what's going on with it now. It was really confusing at first.

Did some more testing today. Caught it misbehaving repeatedly on a track. It's not even control inversion, you can ONLY pitch up until you trim down with the china hat, or you pitch up like 70 degrees, and then it snaps downwards. The autopilot panel can be in any configuration and this issue still happens. The misbehaving bit seems to be the gyro block. When the gyro is off and the bug is not triggered, the trim hat does not function, and you can't make the bug happen. Once you set the gyro to GM, the trim hat starts working and you can trigger the bug. If you've triggered the bug, turning the gyro off does not restore normal function of the cyclic stick. Trimming down with the china hat is the only way to resolve the issue without risking loss of control of the aircraft. The gyro does not have to be synced to cause this issue, just turned on. Hope this is useful to the polychop guys, or to anyone else who runs into the same issue and is wondering about it. (I bet it's fixed already on the other code branch) pitchinversiontesting.trk

I've seen this before, though not on a HUD (and I don't play with HUD's in real life, so grain of salt here.). Projecting an image onto a medium that is not parallel to the projector results in what is called the Keystone effect. This effect occurs no matter how you focus the projector. https://en.wikipedia.org/wiki/Keystone_effect Keystone is a well known issue, and is pretty easily corrected for by either distorting the image being projected, or by shifting the lenses around to align things. I did a lot of this kinda stuff with boardroom projectors. As for the question "does the Gazelle having no keystone compensation for the hud pipper?" I've no idea if that is the case or not. It could very easily go either way, but my gut says they'd adjust for the keystone instead of leaving it. Guess we'll find out when polychop hears back from people who actually fly em for real.

So. I must be doing something wrong, but I'm not sure what. :( Version 2.0.2.52658, Non-steam no mods hot start from parking spot on a rainy morning in nevada. Tested in single player only. Reliably reproducible. At 60 seconds and 260 seconds in the track, you will see me attempt to leave a stable hover by pitching the helicopter's nose down by pushing the cyclic forward. Instead, the nose pitches upwards. Before 260 seconds I even engage and disengage auto hover, to make sure it's not engaged. Continued forward pressure on the stick will continue to bring the nose up until it suddenly pitches violently downwards and normal cyclic pitch operation is restored. Reproduction steps: Fly forward at any speed. Trim helicopter into a stable hover with trim hat by trimming the nose upwards until forward motion stops. apply forward cyclic, nose will pitch up. Workaround: Trimming the nose down below the horizon with the trim hat appears to restore normal function of the cyclic pitch without extreme unintended pitch inputs. Additional note! This happens with or without SAS engaged (flipped master switch off on the main panel. PA caution light illuminates.) I saw a previous posting saying this could be SAS fighting you, but I did another test flight with SAS channels disabled and could still reproduce the issue. It seems that trimming to the limits of the trim hats ability inverts the cyclic input? Joke: I practice religious sex. I get on my knees and pray, and She never answers. pitchinversion.trk