topdog

You're welcome. 1. Start > Programs > Accessories > (Right-click "Run As Administrator") Command Prompt 2. Check what the extension is associated with in case you want to put it back later (replace .txt with the extension you're interested in, I'll use .txt as an example):- C:\> assoc .txt .txt=txtfile C:\> 3. Remove the association by using the = sign with nothing after it:- C:\> assoc .txt= C:\> 4. Putting it back again later if desired:- C:\> assoc .txt=txtfile .txt=txtfile C:\>

If you want to zip up your files and attach them, I can do a quick compare with one of mine. Seems my .pr0 files are just 'plain text' and so should look a little something like this:- [profile=DCS-BlackShark version=0x00000003 [controllers [controller=1f732691-3bc6-41ec-a977-c5bf0b03a3dc group='Flight Control System' [member=75bb6cc8-fb40-4be1-bf2b-4b10397a98a8 name=X52Pro shortname=X52Pro] [controls [button=0x00090001 name=Trigger] [button=0x0009000F name='Second Trigger'] [button=0x00090002 name=Launch] [button=0x00090003 name='Fire A'] [button=0x00090004 name='Fire B'] [button=0x00090005 name='Fire C'] [button=0x00090006 name=Pinkie] [button=0x00090007 name='Fire D'] [button=0x00090008 name='Fire E'] [button=0x00090009 name='Toggle 1'] [button=0x0009000A name='Toggle 2'] [button=0x0009000B name='Toggle 3'] [button=0x0009000C name='Toggle 4'] [button=0x0009000D name='Toggle 5'] [button=0x0009000E name='Toggle 6'] [button=0x00090010 name='Mouse Fire'] [button=0x00090013 name='Wheel Button'] [button=0x00090011 name='Wheel Scroll Up'] [button=0x00090012 name='Wheel Scroll Down'] [button=0x0009001F name='Clutch Button'] [slider name=Mode [button=0x0009001C name='Mode 1' latchable=false] [button=0x0009001D name='Mode 2' latchable=false] [button=0x0009001E name='Mode 3' latchable=false]] [hat=0x00010039 name='POV 1'] [hat=0x00090014 name='POV 2'] [hat=0x00090018 name='Throttle Hat'] [axis=0x00010030 name='X Axis'] [axis=0x00010031 name='Y Axis'] [axis=0x00010032 name=Throttle] [axis=0x00010035 name=Twist] [axis=0x00010034 name='Rotary 1'] [axis=0x00010033 name='Rotary 2'] [axis=0x00010036 name='Precision Slide'] [axis=0x00050024 name='Mouse X Axis'] [axis=0x00050026 name='Mouse Y Axis']] [shifts [shift=cd957a00-26bf-4577-89ff-676166fe3b28 name='Weapons Active' [selectionset [buttoncombo [buttonhid=0x0009001C]]] ...

On Vista, my SST software expects the .pr0 files to be found at this location:- C:\Users\Public\Documents\Saitek SD6 Profiles Hopefully you don't have some oddity with older vs. newer SST versions where the file format changed or something. Despite me having seen elsewhere that the .pr0 files are a kind of temporary file and the .dat is the 'real deal', it seems my version is only working with the .pr0 files. So... bit of a long shot, but if the location doesn't help, you could try changing your *.pr0 files to *.pr0.bak, rename your *.dat files to *.pr0, and then see if it likes the content of those files whilst using that different extension (this depends on how the SST profile editor was written, it may not help at all unless it makes assumptions of the file format based on its extension, but I thought worth a try?). If it doesn't work, revert the filenames back in both cases and I'd suggest knocking on Saitek's forum's doors here: http://www.saitekforum.com/index.php Unfortunately it seems to take them a while to activate your forum registration with them, and you have to contact/email them to do so.

For now, it seems you can follow the BlackShark manual installation instructions: http://lomac.strasoftware.com/tacview-bs-en.php I found it built the *.txt.acmi files in my Lockon FC2's \temp directory fine after that. Note: not a typo about the blackshark thing, using the lockon version of the tacview???.lua file doesn't work, so you need the blackshark one, and to put the dofile("./Config/Export/TacviewExportBlackShark.lua") entry in the end of your export.lua, along with the other instructions/changes. Then it seems fine.

Look in registry under HKEY_CURRENT_USER\Software\Eagle Dynamics\Lock On 1.1\Path and see if it has appended \lockon.bat to the end. If so, remove just the \lockon.bat part and try again. Worked for me, I had installations from LO Gold CDs installed too.

Here we go:- As soon as I removed the \lockon.bat from this registry location and re-ran the setup.exe it was fine.

I have Lockon, FC, then FC1.2 all installed under separate locations. I'm getting the same message upon attempting to run the setup.exe in Vista and have tried it with a right-click and "Run as Administrator" too in case it was permissions related. Going to fire up filemon/regmon and see what it thinks it needs...

This is an option too:- http://support.microsoft.com/kb/841290 I realise there are a zillion like utilities (I used an ant script myself..) but some people might be like me in that they'd prefer to download from certain 'trusted' vendors where an easy option to do so is there.

For a way to view any of the vehicles with some basic UI capabilities to spin it around and get different angles, there is the modelviewer.exe file that's in your KA-50\bin\stable directory. KA-50\Bazar\World\Shapes is where you'll find the various models of the weapons and vehicles and so forth (when you click the Load button in the modelviewer to locate a .lom file). Ok it's not the sexiest multimedia encyclopedia interface or anything, but it might help for getting different angles of a few key ones you're interested in. Type 'clear' and press Enter in the Command: text bar before loading subsequent models or you'll end up with trucks riding on top of hinds and all sorts otherwise :)

I'll wait a month or two, and see how many (more) Starcraft 2 beta players toast their cards still before I give in to an upgrade..

Some hackery in DX10+ would make sense, thanks, I'd like to read more on the inner detail of any 'affinity trick' if someone has it though.

Is that true if you disable HT too? My memory is hazy (XP is, after all, over 8 years old and Windows NT is over 15), but I thought it had the capability and was just soft-locked (license limitation) to 2 CPUs for SMP. Pretty sure Windows 2000 Pro with my dual Slot-1 P2 400's I could do it even heh (that machine is still around somewhere I should see if it works). A quick google (which does point out that XP Home edition can't do more than 1 physical CPU, something I wouldn't have been aware of) produces plenty of bytes saying it can:- http://searchwindowsserver.techtarget.com/tip/0,289483,sid68_gci1189223,00.html http://www.tomshardware.com/news/microsoft-windows-xp-vista,6895.html (actually declares XP as the fastest Win OS in this regard, at time of publishing a year ago) http://www.tomshardware.co.uk/forum/246654-10-windows-quad-core-processors http://www.microsoft.com/licensing/about-licensing/multicore-processor-licensing.aspx Also seems it is referring to physical CPUs as a distinction in the licensing, so it probably isn't even bugging out over a 'faked CPU' via HT. Did I misunderstand what you meant by a system level problem?

I've found vbulletin to do that behaviour elsewhere too, not just here. Since the 'elsewhere' is a website I'm the admin of, I'm kind of stumped how to fix it myself even heh.

Consider this a pledge for a pair of #3's, assuming postage to uk mainland addresses isn't out of balance.

Load up the mission that's taxed your system the most and tab out to desktop to see what the memory utilization is like through it. You can also check to see if page faults are going through the roof in task manager (PF Delta for system process and black shark should spike a few thousand here and there, but shouldn't start chugging with a stream of constant PF's in the thousands non-stop, that's a sign you're starting to thrash even before you might feel it). Throwing RAM at a PC if you're not already using all you currently got, may yield zero benefit for you. I'm only playing with 2.8GB usable RAM in Vista (thanks to 32-bit memory architecture limits and fat video cards), but I'm not in danger of running out of RAM, and that's whilst using no caution in running additional surplus background junk that I could live without.

Here's where I go for best results (w/TrackIR5). Camera is positioned on top of monitor between 25-33% in from the left side, and clip over my left ear. They are almost lined up (by twisting the camera a little, it's not precisely parallel with the monitor face) except I have to point the camera down a little bit as it's above my head. Within the calibration software, switching to camera view, you can see I've almost got the dots on-center but not quite; works well here though. Also note the orientation of the dots, the low dot is placed just about between the upper two on the X-axis. Having it somewhere between them is OK, go outside of that and the device might have some limitations on the extents. That works best for me anyway, and I was able to do the motions you describe OK (until I zoom in close enough to the monitor screen to slip off the camera's viewport). Make sure you've got something close to that. This is also using the default profile/settings, no major fussing around.

Trying to be too clever with export.lua, and finding out that the clickable cockpit is still nice and clickable that way, long before taking control of the aircraft in a training mission / track replay, and so able to crash the aircraft because one of those switches was the AP Alt Hold channel. It's like I just added my own virus to the heli's onboard computers causing them to 'crash' big time. :doh:

Glad you got your answers Gonzo. I was intrigued as to why I couldn't play the track (since everyone else was doing so fine) and I've found out now heh, was all my fault. I have some trigger-based code I'm debugging at the moment and it was turning on the Alt Hold AP at the start of the track heh, so basically your pre-recorded flight was now at the mercy of fighting against the AP that wanted to stay on the ground... that's a definite :doh: on my part. May even be worthy of the Pikard double-facepalm. I didn't even realise those commands would work prior to 'take control'.

Flaming Cliffs 2: About Flaming Time

Still can't play it, same thing happening. Was it a couple of left turns / waypoints into the flight by chance, as you were climbing over a hill where the instructor says something about friendlies nearby checking on the wreckage? If so, I've had a few crashes there either caused by some kind of turbulence + low height (~30-50m above ground on the hillside) + high speed or a bug. I was never quite sure if it was a real mechanical failure or I'd hit an invisible wall in the scenery - the effect was similar either way. After routinely doing that about 3 times I figured I'll give it a wider berth, flew higher, and all was well.

Heh.. I tried playing it, took off, kinda, drifted left past the 2 trucks nearby, then promptly stacked and rolled around the ground into the fence... I'll try it again, I might have been overzealous with the fast-forward keys perhaps.

If you mean in DCS:BlackShark the multi-position switches and dials do go both ways, forward and back, you don't have to keep going forward, forward, forward until it wraps around. Left-click and right-click of the mouse in the cockpit on those controls will usually take you counter-clockwise or clockwise through the cycle as appropriate. Are you just feeling that the keys themselves aren't available to emulate this as well, or just didn't know you could do that?

Interesting, but requires maintenance any time a new non-English forum is added. Using the parent forum value alone should pull up all sub forums within it too, so you can do it inclusive for 'this forum and all sub forums' (as per my example) or exclusive for 'not this forum' (the style you presented). Presumably you can mix and match both styles even; if you want to trim further, but I've not needed to - yet.

Actually that didn't work as well as I'd hoped heh. But try this:- http://forums.eagle.ru/search.php?do=getnew&f=53

My recollection of vbulletin code is that the New Posts is just a shortcut to a predefined Search criteria. So you can define your own Search criteria that uses a forum subset, focused on new posts (in the date options), and then save it. It's not exactly the same since it wouldn't change the behaviour of the New Posts button itself but it's a close 2nd.