loke

After installing DCS World (and buying all the extra modules), I got the "invalid hardware code" error. I ran the registry removal script, re-authenticated everything, but I'm still getting the same error. Here's the steps I took (from memory): I had BS installed, with BS2 (1.1.1.1 update) installed on top of it. I also had Lock On (disc version) installed with the FC2 upgrade installed on top of it Hardware was upgraded (new motherboard, CPU and graphics card) BS still worked perfectly I purchased every single DCS module. I installed DCS World, Ka-50 1.2.2, FC3, A10C 1.2.2, P51D 1.2.2 and CA Ran DCS World. It asked me for all the license keys When it requested the Ka-50 key, I got the "invalid hardware code" error. I uninstalled every single DCS related package (including Black Shark and Lock On) Reinstalled, got the same error Ran the registry removal script Ran the all the applications and modules to re-licence everything Black Shark 2 (standalone) licensed correctly. At this point I've lost 2 or 3 activations due to my testing Still, when running DCS World, BS 2 still refuses to run with the same "invalid hardware code" message Does anyone have any suggestions what to do? I emailed support several days ago, but I have received no answer (are they closed for christmas?). I don't care if I lose activations as I've already accidentally bought another BS 2 license during my tests.

As far as my experience goes, the aspect does not describe the aspect of the monitor, but the aspect of the pixels themselves. Your monitor has both wider physical dimensions, but also more horizontal pixels, leaving the aspect unchanged.

Today I went to the local game store, mainly to look for some PS3 games (yes, I do play those as well :-) ) and what do I see on one of the monitors? A trailer for Black Shark! I never thought that I'd see trailers for this sim in a store like this. The sad things was that I didn't see any boxed copies of the sim though.

I'm using the thumbstick on the Cougar throttle. The stick is analogue, and for a while I tried to use it as such (mapping the axis in the axis configuration of Black Shark) but it never worked very well. The behaviour was very strange, in that it sometimes was moving too fast, and sometimes I wasn't able to make it move fast enough. I ended up not using the analogue control and simply configure the it to behave like a standard hat-switch (mapping the directions to the keyboard controls). It works pretty well, and just like you, I use the HMS for approximate positioning and then use the thumbstick for the precise movements.