Jump to content

topdog

Members
  • Posts

    493
  • Joined

  • Last visited

Everything posted by topdog

  1. I will try out this sorcery soon - thank you!
  2. I think this was the post I had been looking for, but not the answer I hoped to see :) I've been AWOL for years and recently returned. Not being able to 'right click' the switches (and the switches themselves not cycling through just left clicks) has made things a bit tricky. So what are people preferring to use for in-cockpit switching (not hotas or keybinds) whilst in VR with (say) a Rift so that the switches can be right clicked? Use the mouse instead?
  3. Not sure what your info is based on but disabling HT in 2600K is unnecessary for anything except epeen overclocks (even then some benchmarks like prime will be quicker with it on and 8 threads, than off with 4). To say that it needs to be disabled for most gaming is (very) misleading, I never once had to on my last two CPUs, and I never once have to on this one either. That's about 8 years worth of gaming and computing with HT on (my first HT enabled processor was bought in late summer 2003). What I would say and wholeheartedly agree on, is that it is just of no added benefit for most gaming, and therefore, an unnecessary expense if you're just interested in gaming that you could put towards a better graphics card or something instead. That's why I recommended the 2500K over 2600K in this case to base a starting spec from. HT as a feature is (currently) more for scientific or highly concurrent multithreaded (e.g. graphics/video processing) app uses.
  4. I don't think there is much to be determined from this, only that an exception was thrown that the executable didn't handle, and caused it to end. In your blackshark's temp folder should be some .crash files corresponding to this, posting the contents of those along with other information asked for in the crash sticky (like dxdiag output) might shed some more light on your issue. If you want to pursue more with windbg you'll need to use more of its features (commands) to do so. Here may be a resource you would find of use, though it's looking at a specific case of a crash dump that just happens to have the same outer signature (not root cause), it might help you to uncover more relevant outputs: http://www.dumpanalysis.org/blog/index.php/2009/06/25/stack-trace-collection-message-box-hidden-exception-nested-offender-insufficient-memory-c-exception-heap-leak-and-ubiquitous-component-pattern-cooperation/
  5. Yeah the bubblewrap was a bit insane :) Took a while wiping down the metal frames too as they're a bit oily (for sea travel protection).
  6. They are having problems reported to them, though. And with my brand of drives, the problem was exacerbated by the firmware upgrade. So; I know for sure the firmware upgrade will screw mine up, what's still left out to the jury to decide is whether or not I share a similar enough hardware to have the fault too. But the BSOD and lost drives problem predate Corsair's release of those SSDs. Some references: Discussion on BSOD/instalbility issues with FW2.06 on Vtx3 Agy and solid3 drives OCZ Agility 3 problems - Firmware? Total recall of Sanforce 2xxx-drives why so many reports of ssd drives dissapearing? OCZ Agility 3 problem And this just seen: OCZ Official Statement regarding hardware issues reported by other manufacturers I will still be careful at this point since OCZ have been mad-defiant to their customers about problems with these drives, and only now are starting to admit there are some (albeit limited) problem drives out there.
  7. Bear in mind the Obutto hardpoints for the seat and frame can be in two different places to gain a little extra distance forward or back, and as I'm sure you've seen, the chair is also on rails like a car seat is, so you can raise the lever in the front and shunt it forward or back to suit too. I tend to use mine all the time on the furthest back settings anyway, with 27" monitors, so I wouldn't worry too much about 24's and with the extra distance you can slide the seat forward to accomodate.
  8. Crushing news to go against the recent burst towards SSDs, but certainly the right thing to do and hopefully other manufacturers with the same controllers (and problems) will recognise the need to follow suit. I refrained from upgrading the firmware on mine from 2.0.2 to 2.0.6 where the majority of problems are being reported (and presumably newer drive models and batches were already shipping with the newer firmware off the shelf), so I may have lucked out there unless they determine my hardware needs sorting too.
  9. I see - I was thinking more like an item (of the correct dimensions) such as this with appropriate wiring done, which wouldn't have occupied a lot of length: http://uk.rs-online.com/web/search/searchBrowseAction.html?method=getProduct&R=0776123
  10. It's all 3D but the 'fall off' effect (as it is in real life) drops away really quick and you can't really distinguish relative distances anymore. Things are just 'near' or 'far'. You do still get an impressively enhanced sense of elevation, which certainly helps judge landings and altitude-impacting manouvres a lot more (or landing ka-50's on the back of boats I find it helpful too). It would be possible to capture some footage and post it somewhere like youtube (I have some captured in fraps already), for those who have 3D tv's that can see such but aren't able to play games due to lack of 3d vision kit/monitor - if interested. Otherwise the free-viewing (cross-eye or parallel) will help show off the cockpit stuff (which can also be seen in video format, not just screenshot), but the sense of elevation would be too muted and lost under such resolution reductions.
  11. I didn't realise they had been made at differing lengths. What I've been after (and don't really have the experience or nous to do it right myself) was the shortest extension possible, barely enough to clear the mini-din sockets to allow for necessary rewiring but at the 15-30 degree angle offset. I'm not keen on the hacksaw/drill or Target methods of putting rotation into the stick I've seen, and would probably throw away a fair chunk of cash trying to get some custom CNC job done with trying to get the threads and such right. With the design being used here, how 'low can you go' do you reckon in terms of extension length? Also I'm unsure if this is something you've decided to stop or take a break from. I still don't have my stick center mounted, as I would need to get this sorted first really. The sooner I can overcome that now the better though.
  12. Maybe Nevada map is being scrapped, prepare to join pod racing on Tattooine in your A10's instead ;)
  13. You may not be required to buy additional RAM either, some boards today that run in higher modes will operate at the lower mode when less sticks of ram are used or mismatched anyway (i.e. 2x 4gb sticks and 1x 2gb stick in a duall channel board, if the bios allows it, will just run in single channel mode instead). Arguably there's not a need today for more than dual channel for consumer systems. As and when that changes, is likely to be a slow process and not something that will obsolete you overnight.
  14. Hexacore would be wasted I think, unless you get one that simply has more per-core brute power than an i5-2500k can give, and even then the quad core equivalent would be ample even if you were to concurrently record your gameplay in FRAPS whilst playing. That said, it's all subjective. Even with my spec and overclock, I can periodically dip down to some pretty lowish framerates without crazy resolutions (only 1920x1080p, not some 6k triple screen resolution nuttiness), but the gameplay seems fine and unaffected by it for the most part - I have no complaints with the performance I'm getting. If I was recommending a PC to someone, I'd probably start out looking at an i5 sandybridge config, then seeing how that compares to an available i7 on the non-sandy boards (x58 chipset?) price-wise, and probably around a 460 GTX starting place on graphics cards for price/performance or the team red equivalent. 4GB minimum, 8GB preferred, and a 64-bit OS.
  15. Saving tracks turns your flight and all the actions you had taken into something that is repeated and played out in full (and even the opportunity to 'take control' and continue the mission from just about any point to figure out what's wrong). The only real issue is that the tracks are sometimes sensitive to configuration differences and .lua file modifications, and especially different versions of the game (or that used to be the case with lockon and blackshark at least - don't know if that's improved in a10c or not). Anyway, give it a try. The track even contains all the mission data so you can do tracks for missions people don't own and it will still play/work.
  16. http://en.wikipedia.org/wiki/Unrar You only need winrar if you want to make compressed files, the command line decompression utility they provide is free(ware).
  17. By regular, you mean something that isn't already designed for a sata 6Gb/s interface (single Agility 3's will bottleneck on a 3 Gb/s interface and I'm not sure how irregular you'd call one of those).
  18. topdog

    Best camo ever

    Wait - you mean there's planes in those pictures? Damn, the camo is off the scale.
  19. The Agility 3 is a slightly smaller brother of the Vertex 3, offering pretty good performance and smaller scale drives at slightly less cost per GB. For instance, 240GB Vertex 3 = 450 quid or almost £1.9 per GB. 60GB Agility 3 is 100 quid, or about £1.65 per GB. Just to keep in mind anyway, I guess it still wouldn't change your current situation.
  20. This is very true and everyone in their car does the same thing; since you're focused at a depth level that is not where the windshield is, imperfections in the glass get muted from your view. It takes a lot of imperfections (such as quite a bit of rain) before you need to do something to overcome the imperfections from obscuring your vision (forcing your focus level to be at windshield depth). You poor souls who are still stuck with 2D monitors lose this, and imperfections in the glass are as in-your-face no matter whether you're looking directly at it, or at the tank a mile away where AT MOST the scratch in the glass would impair the vision to the tank for ONE eyeball, not both, and since it's not the point of focus, the picture your brain is given will barely be able to perceive the fault.
  21. What's funny is when I watch a track replay now (doesn't happen with vids, but does with tracks), I feel compelled to 'look around' and get momentarily confused when the screen stays still. That's immersion alright :)
  22. I'm not sure on the peak power differences between sandybridge chips and other processors, but I guess the amounts aren't likely to be radically crazy between those and i7 920's. With an overclocked i7 2600k and a just a bit over stock (pre-clocked, not OC'd it myself) 580 GTX SLI I would just be able to get away with an 850W PSU so long as it was good (or very good) quality and not too beaten up age-wise. Something I was looking into myself recently as it happens (but haven't tried as I'm sticking with the single card for now anyway), but there wouldn't be much headroom for deterioration so I might have to replace the PSU after a couple of years if I did that.
  23. DanielH: Well, hello there Mr Wingman ! Wingman: Who are you and what have you done with my flight lead? I know you're not him, he's a mute.
  24. They key for me with a UK keyboard is: #
  25. I believe it working before would have to do with it being confused about which game is actually running. I've had the nvidia driver think my blackshark was WRC 2010 (perhaps it had been just observing the way I fly...), and when the DCS games change their .exe names they can be mistaken again. So combination of newly released app with changes and updates to the driver = stopped working along the way with an unofficial setup, and now needs an official setup or a manual workaround. The other strings are unnecessary, maybe useful to other games, maybe useful to your own personal preferences, but best left unset through the registry. For Win7 64-bit, just to confirm, the correct place to create the link1 string is here: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D\GameConfigs\dcs Edit: Just to be 110% sure of where the path is, and how the registry data type and content should look like. The StereoMemoEnabled is NOT something I put there manually; that appears once you're in the game, have it working, and then press Ctrl+F7 to save your 3D Vision config. Won't hurt either way I guess, but just to confirm only the link1 entry was put there manually to get it to start working normally.
×
×
  • Create New...