P3D Viewer by BIS

[[aps]gnat 28]

Back in time, can't remember when, ArmA2 (patch?) came with a P3D file Viewer

Called "ArmA2 P3D viewer"

You will likely find it in your File-RightClick menu under "Send to"

Unfortunately it seems to no longer work for me.

I get a config No Entry error and a Shader error.

Is it working for anyone else?

Any idea how to get it working?

I ask because I had the idea of making a GUI front-end that indexes all/some your P drive p3d files, then lets you quickly sort through them, previewing them with this P3D Viewer.

[[aps]gnat 28]

Grrrrrr !

Trying to use this view "resets" something. My arma2oa.exe "buldozer" came up with shader errors etc.

Had to copy the lastest arma2oa.exe and dePBO the ArmA2\Expansion\Dta\Bin.pbo into my P drive again so my O2 preview would start working again.

[fuzzysquirrel 10]

No point in making a new thread, I tried what you listed above Gnat but it still doesn't load. Still has the same errors. Any ideas?

[[aps]gnat 28]

Nar mate. I gave up.

I'm guessing its similar to the O2 "buldozer" issues. When this viewer is run, its maybe looking for certain BIN or DTA files with respect to THAT (old?) version of the viewer EXE.

But maybe BIS are no longer updating this viewer EXE in line with the support files which are updated with each patch .....

[Synide 0]

The send-to-viewer thingy wasn't a seperate .exe application. From memory it was just the ArmA2 tools installation program creating a registry entry for doing the 'send to'.

This registry entry is looking for the original filename of buldozer.exe.

As you've copied the arma2oa.exe and it's complimentary bin.pbo\shaders over to your dev drive and altered you O2 settings to use this as your O2 viewer the registry key for the 'send to' is still pointing at 'buldozer.exe'. I'd guess you still have the original buldozer.exe sitting there on your dev drive but of course as soon as it runs it will be getting a mismatch with the 'new' bin.pbo\shaders you currently have sitting on the drive.

All you should (probably) need to do is find this registry entry for the 'send to' and alter it to run your arma2oa.exe instead of what it's currently trying to run and you should be ok... possibly... the game.exe IS slightly different in functionality to the buldozer.exe supplied with the A2 tools.

Once you've done this... if the send to functionality doesn't perform properly with the game.exe running in buldozer mode then you could revert the registry entry to point back at the buldozer.exe.

There is a way to have both the original buldozer.exe + it's original shader files AND your new arma2oa.exe & it's shader files operate on the same dev drive. That's a bit more explanation... hopefully won't need to... give the above a try and as said if it doesn't operate with the arma2oa.exe then I'll try explaining how to set this alternate method up for you.

Unfortunately, during the A2 Tools install I've never said 'yes' to the install question regarding the 'send to' feature so I don't currently have the registry entry on my machine otherwise I'd tell you exactly where to find it.

In your last post...

But maybe BIS are no longer updating this viewer EXE in line with the support files which are updated with each patch .....

Have BIS been updating the dev tools with each game patch? I don't think so... The dev tools (and content on the dev drive) doesn't get touched by any game related patching I believe... could be wrong there. They haven't been 'touched' officially I think since 'BI_Editing_Tools_2_Setup.exe' came out almost 2 years ago.

Personally, I always disliked the 'send to' feature myself but each to there own...

Edited May 21, 2011 by Synide