mattpeckham

This got it working for me, except you can skip the first two steps. Thus: 1. Install the full-version beta 2. 2. Run the beta 2 patch. 3. Run the beta 3 patch.

I know it's not modeled in the BS, but as an RL rookie pre-pilot working on his private aviator's license, you learn there's upwards of 15-20 minutes exterior inspection work (say in a Cessna 172B) running through particulars like eyeballing rivet integrity and poking "shot glasses" under the wings to check for inappropriate separation in fuel mix. Anyone know how elaborate these procedures are and how long they take in something like a Kamov? Are they 100% handled by the ground crew? Or does the pilot have a role in any of it?

Confirming this bug. Another way to trigger it is if you hit ESC to pause the sim then ESC again, you'll hear very loud audio, but if you then hit F2 for external view, then F1 to slip back into the cockpit, everything is (correctly?) muffled.

I'm losing my groundspeed in the HUD at startup too. How do you calibrate this properly again?

Radiotechniczny System Bliskiej Nawigacji (RSBN) Soviet-designed navigational aid? (And yes, I have no idea what that is either.)

I know it's blasphemous to suggest this, but you guys ought to consider licensing the salient bits of the engine to someone with a decent track record to put the arcade face of BS with perhaps a more dramatically developed (narratively speaking) storyline on one or more of the current consoles. You've seen this, right? Similar idea, I think. :)

Another thing: I try to analyze these sorts of games without benchmarking them too rigidly against past or hypothetical future ones. It may be that a dynamic campaign worked well in Game X, but that doesn't mean "dynamic campaigns" as a design principle are this cumulative feature that every game or sim ought to be striving toward. I can even see the value of excluding a dynamic campaign if your design goals are iterative, or "staged," as in BS's campaign. Sure, that might mean it won't always appeal to someone who wants to bury themselves in a drawn-out, dynamic event. But that may just be a player/game mismatch, not necessarily a violation of the sim's internal grammar.

Red Tiger's got it precisely right. Dynamic campaigns in general are hugely overrated and gamey, and not necessarily more difficult. Think of Black Shark more like Combat Mission (also lacking a dynamic campaign, or if memory serves, any sort of campaign system whatsoever). CM's focus was on tactical fidelity in the ASL vein. BS's focus is on avionic and aeronautical fidelity in the military-simulation vein. Both games have a kind of asymmetric structure. I'm still working my way through flight school, so no opinion to share on the ground-based unit AI, but as long as it's basically competent, I'll be happy. Half to three-quarters of the work in real life flying this sort of helo is pre-planning and more micro-strategic than tactical reactivity anyway. I'm hoping a sizable number of the missions also model the helo's priority as a battlefield surveillance and infantry/armor information relay tool. I don't recall Hollis's Longbow and Longbow 2 having all that brilliant ground unit AI, though the dynamic campaign generator was pretty fancy, for all that word's worth in late 1990s context.

Or in my case, new-wannabe-pilot. :helpsmilie:

Yep, we both mean the same thing, just slightly altered semantics. ;)

Nope, cyclic. "Physical" cyclic = real-world joystick, ergo the joystick's throttle. :)

So I was practicing my startup procedures this morning, and...well... Ladies and gentlemen, always start with your physical cyclic's throttle at idle, not maximum. :doh:

I haven't vetted every last one, but all the training missions seem to be automated, while many of the actual missions have the Ka-50 revved and rocking. Any in particular you guys are using to freeform practice going through preflight and powerup, and then to practice spinning around sandbox-style?

19" LG W1952TQ @ 1440 x 900. I need the extra desk space, plus 1440 x 900 = "no frame left behind."

Sim only, not that I'm competent to play at that level. Yet.

Just what I needed, thanks Prophet!

Put it this way: I was toying with the idea of switching back to XP for performance reasons until I discovered the multicore trick. As someone else put it, Vista < XP < Vista 64 multicore. Someone can correct me if I'm wrong about that, but I'm pretty sure you need Vista 64 for the multicore trick.

Hear hear for getting the A-10 out in '09! :)

Fantastic work Wombat! Just verifying that the utility works great on an i7 940 (overclocked to 3.85GHz) running Vista 64!

I think you found the fix Mxyzpylk. I just tried setting 0,1 and it holds, whereas anything set above core 1 sequentially seems to result in a total multicore wipe to 0. Summary: Use PriFinitty under Vista 64, only check cores 0,1, make sure there's a tick mark in auto-set, and you're golden! Update: Hmm, looks like 0,1 isn't providing the same frame boost as 0,2... Note that I have an i7 940, so YMMV on an older Core 2 Duo. Unfortunately I'm still not able to use PriFinitty with my i7 without alt-tabbing out to manually set to 0,2.

Are you sure it's not produced anymore? Saitek still sells them through GameShark. Newegg also has them stocked in the U.S. at the moment. I have the Saitek X52 Pro system myself, along with Saitek's yoke, throttle, and rudder pedals, but they're all sadly boxed and in storage indefinitely back in the States while I follow my wife's career here in Oxford (UK). My fallback this side of the puddle? The Saitek AV8R.

Same problem here Mxyzpylk. I've tried variations (0,2,4,6 vs 1,3,5,7) without success. Curiously, if you watch when it first starts to load the DCS engine, you'll see the utility in fact auto-set the multicores, then just before the final loading screen comes up, I see that switch back to just '0'. So the issue seems to be that PriFinitty auto-sets as soon as it detects DCS.exe, then some internal routine in the program makes a processor check *after* that and resets it 0. You almost need a time-delay setting on PriFinitty so it waits to do its business until DCS.exe is finished loading you into the sim.

If you're looking to apply the "core affinity" trick, I believe Vista's the only place it works at the moment. The difference is astonishing. I'm running an i7 at 3.3GHz with a GTX 280 and DCS chugs at 1440 x 900 on max detail in the Winter Attack demo when panning around the Ka-50 and facing toward the rearward mountains. Enable a second core under Vista, however, and it rarely drops below 30 fps! :thumbup:

Has anyone had difficulty with PriFinitty_1.1.3 getting it to auto-set when DCS.exe launches? I have it set as a favorite with 'auto-set' checked, but for some reason it won't auto-configure the '0123' affinity setting unless I drop out and manually tell it to.