Murphyd

Corbu, Can I ask what extension you're using and where you got it? I'm using a straight extension so stick position isn't ideal.

Hi Dogmanbird, I found this thread whilst looking for something else and saw your unanswered question. In case you're still wondering, there is no initial stiction or break-through that I can detect. I'm running mine in dead-stick mode for flying the Apache and Huey i.e. move stick, let go, it stays in place. I would however note that for significant inputs, I tend to press and hold the force trim release button which in my setup gives completely unrestricted movement until I release the button. I played with numerous configurations (so many control options available) and never quite had something I was completely happy with so decided to try another users profile which I found on the VP Force discord which worked beautifully. The Rhino when compared to the Virpil CM3 and Orion2 clutch based bases (I've owned both and both had horrible stiction) is absolutely God Tier for helicopter flying.

Just an FYI the solution above by Magoo5150 also works for mounting the Orion2 throttle to the MonsterTech plate for the TM Warthog Throttle. The only difference being that you don't need to use any washers with the 16mm M4 screw due, I presume, to the MonsterTech plate being a few mm thicker than the j-pein.

Another article on the subject here; http://arstechnica.com/tech-policy/2014/02/dod-aims-to-scrap-a-10-to-keep-f-35-alive-in-new-budget/ I wonder how much of a game is being played here. Choose a much loved, well respected platform and announce its demise specifically in the hopes of generating a massive backlash and swaying opinion against the proposed cuts overall.

Warthog Hotas + CH Products Pedals.

I've been avoiding watching this as there have been sooooo many different versions that I'm getting quite bored with the clip. This however was properly funny. Loved the comment about EA. Well done that man :) -- Murphy

Where's the "When it's ready" option? ;) -- Murphy

I'm amazed that nobody's written a smartphone app with an "IT'S OUT" push notification yet :) -- Murphy

^^ What he said.. :) -- Murphy

Speaking on behalf of junior members everywhere, I mean those junior members who object to being called junior members by those junior members who insist on calling other junior members, junior members, I'd just like to say... Dammit. I've forgotten my point. -- Murphy

I'd definitely buy a set. -- Murphy

Not sure if it's relevant to the issues others have been describing in this thread but following an upgrade to the 12.1 drivers, I experienced all sorts of graphical and memory weirdness including; - Green screen flickering on mission start-up - Occasional graphical artifacts - Game crashing with out of memory errors - Occasional BSODs Interestingly, performing a complete un-install of the AMD Catalyst suite then running a driver sweeper to remove the remnants followed by a clean install (rebooting between each step) solved all of the problems. The game is now running perfectly. -- Murphy

Just tried this myself and confirm that it works. I changed the monitor lua file to keep my camera on the left hand display (1680x1050) with the ABRIS and Shkval on the right (1280x1024). Have not yet had time to check for any performance improvements but the "Controls" (CTRL-ENTER) panel and frame rate counter are both visible which is a very good sign. Vista 64 Ultimate Samsung 226BW - 1680x1050 Viewsonic VX922 - 1280x1024 -- Murphy

I was clearly on the right track :doh: -- Murphy

What operating system are you running? XP or Vista? If it's Vista, where is BS installed i.e. full path name. My best guess is that you are running Vista and the screenshots are failing either because they're being saved to a location you don't know about or the game is unable to save the screenshots due to having insufficient permissions to write to the appropriate directory. -- Murphy

Hi Kaitsu, Are you running BS with multiple monitors? If so, the FPS counter won't be displayed and attempts to take screenshots can cause a crash. Both are known issues. -- Murphy

I'm neither a games publisher nor an "Interactive Entertainment" analyst but I'd be happy to put forward the suggestion that whilst production costs have no doubt increased so too has the potential market and therefore the average unit sales for successful titles. I'm also a bit unsure about your assertion that prices have remained static in the last ~20 years. -- Murphy

That would be "you're". Can I have the pedantic medal now? ;) /duck -- Murphy

Blackshark is a standalone product. It is available for purchase now in most if not all major regions. -- Murphy

I'd definitely go along with Tharos and TheMoose on this. Your two graphics cards will be fighting for bandwidth on the PCI bus and in all likelihood, generating a lot of contention resulting in their respective frame rates being hurt. SLI, Crossfire (and probably TripleHead2Go?) multi-gpu solutions work cooperatively thus avoiding this contention. -- Murphy

Look on the bright side - you'll be ahead of the curve if the devs decide to implement the changes ;) -- Murphy

Ranger, You have not read the original post properly. These are proposed changes to the current LUA configuration files. Nothing more. -- Murphy

Hi Chibawang, Are you running full screen or windowed mode? I believe that there are numerous potential problems if you run multi-monitor configuration in full screen mode on Vista systems. Regards P.S. According to my understanding of how this works, I believe that your config is wrong. When running in multi-monitor mode, BS behaves as if there were 3 screens, the first of which (a virtual or "ghost" screen) is located at x=0,y=0. The second (your first actual display) will be located at x=display2_X_resolution*,y=0 and the third at x=display2_X_resolution+display1_X_resolution,y=0. Confused? You should be :) Imagine 3 displays, d1, d2 and d3. d1 is virtual, it is created by BS. Its resolution is that of d3 (which is your actually your second monitor). For example, monitor 1 = 1680x1050 and monitor 2 = 1280x1024. With this setup, to place your Shval on monitor 1 and camera on monitor 2, you need to shift everything right by the width of the ghost display which, in this example is 1280 pixels. Description = 'Shkval on the left monitor, camera on the right' Viewports = { Center = { x =1280+1680; y = 0; width = 1280; height = 1024; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } } Shkval = { x = 1280; y = 0; width = 1680; height = 1050; } It looks like both of your displays are 1280x1024. If this is the case, your actual config should be: Description = 'Shkval on the left monitor, camera on the right' Viewports = { Center = { x =1280+1280; y = 0; width = 1280; height = 1024; viewDx = 0; viewDy = 0; aspect = screen.aspect / 2; } } Shkval = { x = 1280; y = 0; width = 1280; height = 1024; } -- Murphy

Don't want to derail the thread but curiosity got the better of me. Is this a newer model KA-50 in the picture above? I'm guessing that the globe is a FLIR system and also that the Shkval is mounted higher in the nose to accommodate this? -- Murphy

My ghost display is 1280 also but I've got an identical set-up to you i.e. main is 1680x1050 and secondary is 1280x1024. -- Murphy