Has anyone figured out how to show hi-res textures in buldozer?

[abs 2]

As stated in the title...anyone?

Abs

[sequisha 13]

Only way I've been able to fake higher resolutions is a workaround. I scale everything up temporarily like 10x.

Observe, ctrl-z wheh finished.

[bad benson 1733]

the key is how you zoom in on the model, at least for me.

so instead of using the mouse to slowly slide towards the model you center it with numpad 5 and then zoom in with the numpad + key. once the textres pop into high res you can use your normal way of navigation. it seems like mipmapping is tied to the zoom level so by being zoomed out by default you get the resolution the model would have ingame when you are at the distance the camera is in at this point.

i hope that makes sense ;)

[da12thMonkey 1943]

the key is how you zoom in on the model, at least for me

That doesn't work too well at all if you have a small-ish scale model.

It used to be possible in old Buldozer to set up your graphics settings (using a User.Arma**Profile configuration file) in a way that would allow you to see un-mipmapped textures at almost all zoom levels, so that you didn't need to piss around with it like that. You just set texquality=4 in the profile document.

However, I can't find where the location of any default settings profile referenced when the new O2 viewer is launched, is. Assigning the -profiles= extension doesn't seem to generate a new profile document in the defined location like it used to do when launching the old version of Buldozer - it only creates a new, empty Arma3.cfg file (which has no graphics settings). And manually placing a User.Arma3Profile document in that location doesn't seem to change anything.

With old Buldozer, you could also just run the standalone Buldozer.exe outside of O2, and press F1 to bring up a bunch of graphics settings options that would update the default graphics profile. But now that the viewer uses Arma3.exe instead of its own .exe, the F1 thing doesn't seem to work in most instances.

[abs 2]

Neither the zooming or the expanding worked for me. :/

I'm hoping that BIS comes up with an update for the tools that allows us to do the things we could with the old o2.

Abs

[NZXSHADOWS 0]

Add these startup commands to your Buldozer.exe in Oxygen.

-profiles=X:\profiles\ -name=Buldozer

Start the viewer an it will make the files for you now the trick is to go into the "profiles\Users\Buldozer" folder an open the Buldozer.cfg file. Paste in

version=1;
blood=1;
singleVoice=0;
maxSamplesPlayed=96;
anisoFilter=4;
textureQuality=10;
shadowQuality=3;
tripleHead=0;
useExtendetInfoType=1;
language="English";
forcedAdapterId=-1;
detectedAdapterId=0;
detectedAdapterVendorId=4318;
detectedAdapterDeviceId=4676;
detectedAdapterSubSysId=358168642;
detectedAdapterRevision=161;
detectedAdapterBenchmark=237;
winX=16;
winY=32;
winWidth=1024;
winHeight=768;
winDefWidth=1024;
winDefHeight=768;
fullScreenWidth=1920;
fullScreenHeight=1080;
renderWidth=1920;
renderHeight=1080;
multiSampleCount=1;
multiSampleQuality=0;
particlesQuality=1;
GPU_MaxFramesAhead=1000;
GPU_DetectedFramesAhead=1;
HDRPrecision=16;
vsync=1;
AToC=0;
cloudsQuality=10;
pipQuality=2;
dynamicLightsQuality=1;
PPAA=0;
ppSSAO=0;
ppCaustics=1;
ppBloom=1;
ppRotBlur=1;
ppRadialBlur=1;
ppDOF=1;
tripleBuffering=0;
sceneComplexity=300000;
shadowZDistance=100;
viewDistance=1600;
preferredObjectViewDistance=1300;
terrainGrid=25;
volumeCD=10;
volumeFX=10;
volumeSpeech=10;
volumeVoN=10;
vonRecThreshold=0.029999999;
gamma=1;
brightness=1;
fovTop=0.75;
fovLeft=1;
uiTopLeftX=0.074999988;
uiTopLeftY=0.074999988;
uiBottomRightX=0.92500001;
uiBottomRightY=0.92500001;
IGUIScale=0.85000002;

Make adjustments that you need an save the file. The main trick is to select the buldozer.cfg an right click select properties and in the Generals tab at the bottom check the "Read-Only" box. If you do not do this O2 will overwrite the file back to default. After all thats done your ready to go. Start The Viewer. But remember when makeing adjustments to the .cfg file dont forget to keep it on "Read-Only" when your not editing it to your needs.

[da12thMonkey 1943]

Tah mate. I think the bit about making it read only was what I was missing.

I had tried adding the TextureQuality = 4 parameter to the Arma3.cfg file generated by the -profile command on its own.

Edited December 30, 2013 by da12thMonkey

[abs 2]

Thanks all! Your way worked perfectly, NZXSHADOWS. :)

Abs