enigmatics

Been out of town a couple days.. still no ideas on ways to get around this.

Grab as many driver updates for your hardware from the manufacturer's websites and install those first before doing windows updates, sometimes that can help.

In several of the training missions the cursor movement goes below the screen edge when using a 16:10 aspect ratio. I am assuming this is because the training tracks were recorded on a computer with a 4:3 display. Is there a way to override the training tracks' zoom level in order to see the hidden cockpit interaction? Here's a little graphic I whipped up to help describe what I'm getting at. Any gauge or switch in the blue area that happens to be referenced by the training mission is off the screen and the in-game cursor gets stuck at the edge of screen.

I'm having the same issue, but I don't think the OP articulated it well enough. When DCS displays at 16:10 it takes the 4:3 image and blows it up to fit horizontally causing the top and bottom of the screen to be cut off. This poses a problem when watching the tutorials in 16:10 as the track will often click on something that had been at the bottom of a 4:3 display but ends up being below the viewing area in 16:10. What I'd like to know is if it is possible to see the full 4:3 image along with the added screen space a 16:10 monitor affords. Will increasing the overall FOV cause the image to look stretched or will it essentially increase the viewing window? -edit - It seems the issue is setting the default FOV, not necessarily the min/max. Is there a way to change the starting FOV so it overrides the FOV of track files, specifically training tracks?

Or disable UAC altogether, problem solved. Also, if a program tries to change files within its own directory and UAC is enabled Vista will route the file to a folder of the same name somewhere in the User directory, I forget where. I can't remember if this was something a program had to support along with vista, either. It's been over 24 hours since I've slept... Otherwise just disable UAC and all your problems will disappear... until a bot takes over your computer...

Might want to try messing with ranges using Modman. There are all sorts of graphical setting to adjust using mod man including near, mid, and long range draw distances. http://www.lockonfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=165&lid=991&ttitle=Modman_7.1#dldetails *requires site registration

Yea. I haven't yet because the dead zone is already pretty big. ...I just tried setting the dead zone to 50% from center, stops all of the jitters but this one point near center where the signal jumps all the way to the right. I'll have to soften the curve significantly in DCS/LOMAC to compensate for such a massive dead zone.

Anyone know where to find this? I couldn't find anything on lockonfiles.

No clue, I'm not sure if I trust myself to take it apart and put it back together still working. The twist glitches all over the place around the center point, but once you get past a couple degrees the jitters soften up to the point where it's manageable. Sounds physical to me, especially since everything else seems to be working fine. Are the correct replacement potentiometers easy to get hold of? Best possible stop gap! Thanks to you I realized what else could be done, so you helped out anyways ;).

Heh, I haven't flown with "all-or-none" rudder since my first days of flight simming. Oh, but that gives me an idea.. I could remap the target designator to a hat and put the rudder on the thumb mouse input on the throttle. That might work.

The Z-axis on my X52 has finally gone to crap after 5-6 years of use. I can't afford anything new for a month or two so I was wondering if anyone knew of a way to fix the stick twist or if there was a different way I could input rudder controls until I can pick up a set of pedals or new HOTAS. Thanks for any help!

Might want to post your motherboard and audio card info. I use the IDT chip that is onboard an Intel DG33TL with Vista Ultimate 64x and 5.1 audio works fine.

Or when flying in valleys and getting close to a steep rise to either side of Ka-50 causing the helicopter to bank away from the slope. That confused me the first time I witnessed it, having only half the rotor disc affected by IGE.

Well, I found exactly what I was looking for.., but it requires phantom power and is kinda expensive. Headset Mic: http://shure.com/ProAudio/Products/WiredMicrophones/us_pro_wh20xlr_wired_content XLR to USB w/ phantom Power: http://www.shure.com/NewProducts/X2u/index.htm Total cost: $200 via amazon.com Oi. /edit - Looks like there is a much cheaper XLR-to-USB device: http://www.bluemic.com/icicle/ which drops the total price down to $120 /edit2 - Or I could get this at the same price as the Icicle which would allow me to input directly to the sound card: http://www.behringer.com/EN/Products/502.aspx I think I'm going to go with this, way more versatility for the money.

Hi all! The microphone on my Sennheiser PC161 headphones broke on me so I'm looking for a microphone to use while gaming but I have a couple requirements. 1. Noise-canceling or mono-directional. 2. Over-the-ear or over-the-head. 3. No ear speakers. 4. I'll look at stand microphones if there isn't anything that meets 1-3. 90% of the time I'm using surround sound speakers and previously I just put the PC161s around my neck to use the microphone. I figure now I might as well get a mic that is lightweight and doesn't have a lot of bulk, but I would still like to have the mic move with my head. I jerryrigged a mic stand with some wire for a traditional microphone, but it just isn't cutting it. Anyone have any recommendations?

Hey, the tutorial claims it can be done in 30 seconds, 45 blindfolded :P. And there is always the cheat startup, Home-LWin. I've never timed myself, but I bet I could cut it fairly close to the three minute mark after the several dozen manual cold starts I've done if I tried. It would be good to know if I had to wait those three minutes or face inaccurate motion detection if I was making a scenario where take-off time was a top priority.

I take it you have to remain stationary during that time?

Woa, Huxley is still in production? That one fell off the radar a long time ago. Disappointing since it was my number one anticipated game for a while. I'll have to check in on it again.

When should the (3 minute) alignment process be used, is it manually started? I don't remember seeing anything about it in the developer vids or the training missions, is it something to even worry about?

Using visual references for hovering or any precise maneuvers in a simulation is not necessarily the best system to use. For one thing, in real life visual cues are supplemented by the spatial movement detected by the inner ear. If you only have one of those to work with, especially after being used to having both senses to work with, accuracy goes down the toilet. Secondly, visual cues in a virtual word are not 100% accurate depictions of the simulated spatial geometry. When you pan from left to right do you notice how the scenery grows as it reaches the edge of the screen? That can have a huge impact on spatial awareness when you are working with very precise and minute control inputs when limited to only visual cues. In my opinion the best system in-game to bleed off speed and come to a hover would be use of the IAS guage while at speeds over 30 kph and the HUD's ground speed indicator (with glances at the ground/horizon if fairly low to the ground) at or below 30 kph. Without the sensation of movement it is neccessary to check the guages frequently to compensate for the lack of sensory input. As for getting the sometimes missing ground speed indicator on the HUD to come back up it almost always only involves a Targeting Mode Reset (Backspace). I've never noticed the issue with too much yaw trim negating it since most of the time when I've had too much yaw I had no clue what I was doing. I was reading is another thread on the forums that for the most part yaw in anything more than small tweaks is actually bad for the KA-50 as it causes a much higher chance for the the two rotor discs to intersect. If you can keep your yaw to a minimum and instead rely mainly on bank turns with touches of yaw I think you will find the helocopter much easier to control, I know I did, plus less of a chace to loose the ground speed indicator. For reference here is the post that informed me quite a bit about yaw and flight mechanics, it is a very enlightening read. http://forums.eagle.ru/showpost.php?p=671731&postcount=12

Ya beat me to it! :P Weird thing though, I paused right before I crashed and hit F2, rotors looked to be in perfect shape.. I wonder if the shaft can break or the little arms that tilt the blades?

Nope, no change in inputs. My thumb wasn't anywhere near the trimmer button. I think I figured out the kachunk noise, when the control started going all haywire after a couple dips I though I might be stuck in a vortex so I tried banking to the right and increasing the collective. I probably pulled on the collective too hard and the kachunk sound was the rotors breaking. Still not quite sure why I started dipping, though. I know for sure I had alt-hold disabled. Maybe I left auto hover on but it didn't feel like I was fighting anything through the whole first 2/3rds of the approach. That seems like the most likely candidate anyways.

While I was performing a strafing run doing no more than 80-100 km/h with about -10 to -15 degrees pitch suddenly my nose started to pull up with no change in input from me and when I compensated the nose jumped up again causing me to push the stick forward even further. All of a sudden I heard a kachunk and my stick lost all control. Anyone know what may have caused this? I had the pitch, bank and lateral dampeners enabled but they did not cause anything remotely similar earlier. /edit - All targets were static objects, it was a custom made target range. So no enemy fire. Collective was around 40%-50%