topdog

This is a specific entry needed for the 3d vision driver to know it should switch on for a10c, because they haven't provided an official profile for it yet. It doesn't interfere with any other titles. Also only the link1 entry is required, the others shouldn't be set. We also need to know your OS to know if that's the correct path, or if your 3d vision profiles are stored elsewhere.

Yeah it has completely replaced my desk in my 'office away from the office' :) It had to really, and I do enjoy buzzing around the racetrack on wheels as well as wings too. I've just been getting lazy and leaving the driving wheel pedals on the ground to use as makeshift rudders instead of swapping them over for the real deal.

Works great like that in Arma 2, and as mentioned, flight sims and driving games (not just sims, I wouldn't call Dirt2 a sim for example,) get good coverage. Also useful if you're prone and want to look around but not move around, messing up your current gun aim/target coverage as well as potentially giving your position away more easily. More FPS should make use of it than does today, but IMO naturalpoint don't really do themselves any favours by making the API a chore to obtain (whilst also trying to force out or at the least discourage competitor options from being compatible when doing so). In terms of profiles I go for something real simple now that just suits me everywhere. Pick the Smooth profile, check Exclusive so it is locked and not switched from game to game, uncheck the boxes enabling hotkeys for everything except Center (e.g. Pause, Precision, don't use any of that malarky). Nothing else to it for me, and I usually bind my Center key to a spare joypad / controller device, rather than to a key on the keyboard though the default isn't too bad/intrusive anyway.

Have you seen this thread and post? http://forums.eagle.ru/showpost.php?p=1030334&postcount=49 The link1 entry in the registry is the important bit for the dcs subkey. If you're using 64 bit Win7 make sure to use the correct path to the key (64 bit includes the wow6432node portion in the path as outlined on the next and final page of the thread). I'm not using the super new beta drivers but I am using the latest released ones and had the problem, but overcome it with the registry entry. Regarding the extra monitor/pit displays, even with trackir, people do find them useful visual cues.

To give you an idea of when you'd be able to play it: By my estimations that would take you just shy of 500 years to input. Without sleep.

Check if you have that VirtualStore folder (and what's inside it) and you'll see where your permissions are limited. It's the only reason the folder gets written to. I should also mention just in case it's not known, that the AppData folder isn't shown by default in your user folder but it will be there. You can access it if you type it into an address bar though, or navigate with cd in the command prompt.

Data Virtualization strikes again. You'll probably find some of these edited and missing files are living in your C:\Users\yourlogon\AppData\Local\VirtualStore\blah (where blah is the normal path to the item from C:, such as Program Files (x86)\Eagle Dynamics\Ka-50\missions\tracks). This was caused by you only having limited permissions with your own normal logon to the location it was trying to write to - for future reference mostly in case you encounter more phantom edits or files that go missing.

Bleh, one last thing to mention - if you were thinking of overcoming the periscope mode by having the 3 monitors in portrait mode, whether it's a problem with all of them or not I don't know but due to the way the polarization of the glasses work, turning them 90 degrees results in massively less light passing through than before, so rather than being ~50% dimmed it's down to only letting about 25% light through. Not good, for that scenario.

minor necro time ! The framerate feels smoother, presumably because you're brain is merging time-delayed frames together. E.g this: L-----L-----L-----L-----L-----L-----L----- R-----R-----R-----R-----R-----R-----R----- Feels less smoothed than: L-----L-----L-----L-----L-----L-----L----- --R-----R-----R-----R-----R-----R-----R--- Each right-eye image has to fuse with a left-eye image to be whole, but which one? I suggest it is merging with a little bit of both probably, and thus the intervals feel more like: L--l--L--l--L--l--L--l--L--l--L--l--L--l-- r--R--r--R--r--R--r--R--r--R--r--R--r--R-- Where this comes crashing down and immersion breaks, is if you're doing something like looking at an area of screen where lots of change is occurring during the low framerate (let's say with trackir on you pan your head from 9 oclock to 3 oclock), the jumps in pixels for each frame are simply too large to happily merge the images together and you now feel like you've just experienced that kind of strobing effect you get when you wave your hand in front of the TV. Also incidentally, the hit for 3d vision (in auto mode, meaning developers haven't implemented their own stereo3d and rely on the nvidia driver to do it) isn't 50%, a 20 fps rate normally would go down to around 15 fps in 3d vision typically. Only part of the rendering pipeline is hacked by the driver, it doesn't do double the work for the stuff that isn't relevant to it. In other words, it only puts the pieces on the chessboard one time, it then creates two different perspectives of the view. Even smarter custom implementations of some stereo3d implementations can minimise the hit even further, but as we all know to get that, something else in the development has to give way. A word of warning about triple monitors though.. imagine having triple monitors, but only viewing them via a periscope. The glasses create that kind of a tunnel for you because the 3d is only going to work where: a) the focal area of your two eyes overlap in the middle b) won't be obscured by the frame and rims of the glasses You'd have to be bat**** crazy hardcore I think to shell out at the moment for 3d vision surround (3 monitors all in 3d vision 120Hz mode). Whereas the benefit of either single monitor 3d vision or triple monitor plain 3d would offer the greater reward for the outlay. One thing I'm curious about is ED's standpoint on stereo3d.. would I be right in thinking it's a nice freebie, it won't get intentionally broken in the future, but it's not being explicitly supported and catered for? I'd like to collate the problems and workarounds of using 3d vision, as each patch can have an unintended but serious impact on this, and it would be useful to know if ED would care to officially recognise stereo 3d issues as real bugs or unsupported. Anyone know?

Hmm.. yes that is right with ide and Trim :doh:. I recalled on my mobo there are 3 modes of operation it'll work in, IDE, AHCI, and XRAID. I know I wouldn't get TRIM whilst in a RAID config but even a single drive not setup for proper Raid 0/1/etc. on an XRAID config wouldn't have TRIM support. I was trying to think of the other reason why I wanted/needed AHCI and other than what you mention, I think it was the Intel Rapid Storage Tech drivers which offer better performance for a vertex3 on p67 chipset than the MS IDE driver would. Those (Intel RST drivers) work only in RAID or AHCI mode I believe, so it was the combination of things that narrowed down my line of thought into believing TRIM = AHCI.

Stuttering can occur when the drive needs to do GC / Trim at inopportune times. One reason for this occurring is if your drive is allowed to go into low power state when it's idle (sleeping the drive when it would normally do it's own background work, means it has to find other time to do this which will inconvenience you). So, as long as it's not a firmware fault (has been known to happen, and sometimes it's the newer firmware that has the fault so look for similar issues and versions), check that your power policy never turns the drive off or to a low power state after inactivity, and if in Windows 7 you should be using AHCI mode for taking advantage of Trim unless your drive has its own built in outstanding garbage collection capability (unlikely I suspect). The other thing that may be worth checking is if there are more than one driver you can use, and if so, to find out which is the recommended one. Some drivers are provided by Microsoft, some by the vendor, some may be 3rd party or (motherboard) chipset (such as Intel Rapid Storage driver tech). I'm not familiar with your particular drive, but look into this nonetheless as it is a known contributor to the performance of the drive.

Also to qualify the use of readyboost, this is for mixed disk environments. If you have SSD only, ReadyBoost isn't even available for you in Win7 it'll be off and unavailable for your system drive. If you have both SSD and HDD, then the readyboost cache is for speeding up the (frequently accessed) data on the HDD, which no amount of RAM can compensate for. So "buy ram instead" isn't applicable. Overprovisioning with a modern drive takes care of the wear-levelling needs I believe, but sure, some slack room won't hurt as the overprovision space is also needed for failed cell swapouts / remapping. In any case, follow OCZ's guide, it's about as valid as advice gets.

Whilst no more than necessary is prudent, some amount of swap can be necessary regardless of RAM, it's just how some things (applications and system operations) work. Writing periodically but random reading small (4k) sizes of data are where SSDs shine, so for pagefile and Windows Search (which is what I meant in Windows 7, didn't mean to be referring to the indexing services) they are actually a prime candidate (this is after all, the premise behind readyboost too). http://blogs.msdn.com/b/e7/archive/2009/05/05/support-and-q-a-for-solid-state-drives-and.aspx http://www.ocztechnologyforum.com/forum/content.php?306-SSD-ABC-Guide --> http://www.ocztechnologyforum.com/forum/showthread.php?79848-THE-BASIC-GUIDE-amp-FAQ-ABC-for-OCZ-SSD&p=567577&viewfull=1#post567577 --> http://www.ocztechnologyforum.com/forum/showthread.php?79848-THE-BASIC-GUIDE-amp-FAQ-ABC-for-OCZ-SSD&p=567582&viewfull=1#post567582 Hope that helps qualify/clarify.

My cheeks hurt (face cheeks!) from the stupid grin I've had on my face whilst re-acquainting myself to A10C after installing 1.1.0.7 + all the goodies (max graphics, 3d vision, trackir, etc.). Hope the final tweaking of the patch goes well and please, whatever it is you're doing, keep doing it :)

For some reason I didn't think it was largeaddressaware but you're quite right: C:\Program Files (x86)\Eagle Dynamics\Ka-50\bin\x86\stable>dumpbin /headers simulator.exe | find /i "can handle large" Application can handle large (>2GB) addresses Thank you.

2GB :)

There's 2 main ways you can go to get good performance. 1) Full-on SSD for everything. 2) Use part of the SSD's space, if the SSD is a secondary drive, for Windows' ReadyBoost which will cache and serve clusters requested frequently from the mechanical HDD. Whether the latter will help with the micro-stutters that have been observed in A10C I don't know, but it's a good method to getting the performance of a mechanical HDD up to SSD levels, it will just take some time for the cache to gain knowledge on the most frequently accessed disk areas so won't be an instant improvement either. Generally speaking it's good to have the following on the SSD directly: 1. OS 2. swap 3. indexing 4. readyboost 5. Any other apps/data you have room for The app doesn't have to be on the SSD necessarily to gain the benefits but I don't have the gubbins or time to test out the variations for precise information on how they compare from DCS' perspective.

Full format isn't necessary, quick format is. If there's any doubt as to whether the drive has ever been used before (or you need to do a reformat and reinstall yourself) then 'format' isn't what you want to do, but an operation called a 'secure erase' which resets the nand flash to 'factory' performance levels. Presumably you have it installed already now, but if you haven't or you might be doing it again anyway to get it right: OCZ's own guides (on the vertex 3 product page is a link to it) are fairly large but very good, I suggest going through it and picking out the bits that are important for you and creating a checklist. Things to importantly check for are partition alignment (though unless there have been significant mistakes, Win7 is good at doing this automatically), and switching to AHCI mode ensuring Win7 enables its Trim support. Tools like AS SSD and Crystal Disk Mark/Info will help report whether these items are on. Having Win7 setup with your SSD properly also helps it avoid doing something stupid like defragging it (this is a fairly big no-no to do) on a schedule (even bigger no-no).

So, had a bit of time off there.. stuff has all arrived (finally - had the monitor for 2 weeks now approx.), been getting to grips with 3D Vision and overclocking and SSDs and Win7 64 bit etc. etc. all at once. I game/compute a lot so after a hiatus it was time to get BlackShark deactivated on my old system and installed here. Verdict: I'm in love again <3 :D Surprisingly few 3D Vision artifacts (surprising in that, as far as I know the game wasn't written with stereo3d in mind, and that there appear to be very few 2D tricks used in the rendering pipeline). I think the biggest/main one I've seen so far is that if you get close to the cloud layer then it renders the clouds near you at screen depth, which almost caused be to crash out of disorientation :D Well it may have been the clouds, or it may have been that I've been trying to fly the Shark using my G27 wheel... don't have my hotas hooked up yet so that proved a bit of a challenge too ("what does this pedal do, oh, it's the pedal that flips me onto my back - ok!"). Good times :D The NVG work OK under 3D Vision mode too, I thought especially that might be one area that might not like it much. If anyone thought the Shark pit was impressive before, in stereo3D it was a whole new beast, very very good indeed.. I'm really quite pumped and going to give A10C a blast now too (I haven't even really had an opportunity to properly play that yet since beta ended). Edit: Sense of altitude is incomparably better with stereo3D too.

IMO the best reason for both is to spur competition. DirectX may not be where it is today had Carmack not shown what the competition was capable of. Then DX set the pace and it's GL that picked up its heels to keep up and keep itself noticed. The more they do this, the better for us, and that's the bottomline for consumers :)

My HafX (greeny nvidia styled - I almost took the black one though) is awesomely quiet. The VGA duct fan was mental when I had it plugged into the motherboard, it was outputting more noise than everything in that PC and the one next to it combined. Once I put it on the PSU headers and moved the side-door fan to its place on the mobo, all perfect (I've since removed the VGA duct fan completely since it'll be blowing back into the end of the graphics card I am using currently and would interfere with its own cooler - this isn't a prob, the duct is optional anyway). No aftermarket fans swapped in or anything, they were good enough in conjunction with a high quality CPU cooler (Noc D14 like yourself).

So long as the GPU fans are pulling air over themselves into the heatsink, then PSU fan face down, you want cool air seeping along the bottom of the case (usually from a front intake fan or side panel fan) and being drawn into the GPU fans uncontested, if it expels out both sides, let a higher exhaust flow take that back out the case.

It works either way; the definining part was whether or not there was a grid/grill/mesh at the bottom to allow for traditional-way-up mounting as an option. I would say it depends on your graphics card as to which you go for, if the cooling on the card has fans that draw air in over the card and expel it out of a rear blanking plate slot, then you want to mount the PSU with fan downward so it's not competing for air with the graphics. If the fans on the graphics are blowing out into the case, use the PSU's fan to draw it through and out the PSU quick by mounting it with the fans facing up (if there's no other exhause fan you can put between the graphics and PSU - unlikely). The PSU fan is for cooling the PSU and not your case; but not at the expense of creating a hot pocket of air from your graphics card.

The most that usually happens is swapping fans with coolers, and even then the results can be mixed rather than improved as some had presumed. Some combinations just don't work well. Thumbs up for the NH-D14 here too by the way, not only brilliant performance, but astoundingly (literally 'is my PC actually on?') quiet without having to sacrifice performance by voltage throttling the fans. Money well spent and I might be replacing the cooler in my other case with one just to shut it up. I actually let one fan be controlled by the mobo so it does get throttled down, but even when I ramp both up to normal levels, anything more than a foot away from the PC case and I can't hear it anymore.

Additionally that command line parameter is interpreted only by specific programs that are expecting it, it's not a general use parameter for any DirectX app.