noob to TH2G..need help

[hannibal]

just got the matrox 300$ toy...

 

but i am having trouble...

or at least i am having no clue...

 

i have a TH2G digital, with 3x Acer x203w, off a 8800GTS G92 512..

 

im not sure what is the ideal setup in windows..

should this be done in triplehead, or indiviual monitor, what resoultion, should be set on that PowerDsk-SE (im runnign version 2.4.0.11)

 

note, i only messed around with windows desktop and FSX so far...

right now my res on windows desktop is 3840x800, 32bpp...

i dont seem to get 5040x1050, or 3x 1280x1024, and i get the annoying black bars on the right and left of the triplehead....

 

i see urze's setup, and it is clean! good bezle managment and good fov!

i want the same!

[hannibal]

ok, i re updated the firmware to the th2g...i can get 4320x900 now...

i went to a link in the widescreen gaming forum...it work...before i did a google search..and what ever link they had had some kind of link to the matrox site..but didnt work...owe well, it works now..

 

sux that my x203w doesnt supoort the 57Hz...i get some message that says input not supported...but it was fine with SoftTH...

 

now i want to get ride of these stupid bars on the side! (i have a feeling that this is supposted to be normal).....URZE what did u do with your setup!

Edited January 12, 2009 by hannibal

[JEFX]

Hannibal,

 

If this can be of any help, look here, I posted a detailed tutorial about Thead2Go: http://forums.eagle.ru/showthread.php?t=31499

 

good luck and dont hesitate to contact me, it is a great immersion experience once it is set correctly!

 

JEFX

[hannibal]

thanks...i have that link...great info..

this is a good link too.. http://www.leftside-limited.com/misc.html

your link looks like the guy has the bar/bands on the side, looking at that second pic down...

also i looked at urze video (ultmate hardware), looks like he does not have bezel managment on, rather just very small monitor physical bezels...

 

anyone that knows how to get rid of bands, let me know..but looks like its here to stay? (someone prove me wrong)

[JEFX]

Hello Hannibal,

 

You are correct about the 'black bands', because when you use Bezel management to link images, you move the image of the leftmost monitor virually to the right and the image of the rightmost monitor virtually to the left, therefore linking with the middle image without gap.

 

The result, is a loss somewhere in the width of the images equivalent to the with fo the bezels...

 

But, if you havent experienced it for yourself, it looks worse on a picture than in real life... The big difference is motion... When everything is right and you use it in the simulator (or any game, I use it with great immersion in FarCry2!!!), you forget both the bezels and the loss at far left and right, because the image moves.

 

The only drawback with a TH2Go setup is finding the right snapviews in order not the get the bezels in the way, but it is quite easy.

 

Hope this helps.

 

JEFX

[hannibal]

ok, i got my th2g to work so far, but for some reason when i zoom out, the screen freezes....

i set gfx cfg

DisplayMode

{

resolution = {4320, 900};

bpp = 32;

fullscreen = 1;

aspect = 4.8;

Interface

{

resolution = {4320, 900};

bpp = 32;

fullscreen = 1;

}

Simulation

{

resolution = {4320, 900};

bpp = 32;

fullscreen = 1;

aspect = 4.8;

}

and the view lua

-- Camera view angle limits {view angle min, view angle max}.

CameraViewAngleLimits = {}

CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 175.0}

CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 175.0}

CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 175.0}

CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 175.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 175.0}

CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 175.0}

CameraViewAngleLimits[PlaneIndex.iA_10] = {20.0, 175.0}

CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 175.0}

and the srver.lua

CameraAngleLimits = {}

CameraAngleLimits[PlaneIndex.iSu_27] = {200.0, -120.0, 90.0}

CameraAngleLimits[PlaneIndex.iSu_33] = {200.0, -120.0, 90.0}

CameraAngleLimits[PlaneIndex.iSu_25] = {200.0, -120.0, 90.0}

CameraAngleLimits[PlaneIndex.iSu_39] = {200.0, -120.0, 90.0}

CameraAngleLimits[PlaneIndex.iMiG_29] = {200.0, -120.0, 90.0}

CameraAngleLimits[PlaneIndex.iMiG_29K] = {200.0, -120.0, 90.0}

CameraAngleLimits[PlaneIndex.iA_10] = {200.0, -120.0, 90.0}

CameraAngleLimits[PlaneIndex.iF_15] = {200.0, -120.0, 90.0}

 

any reason i start to freeze when i zoom really far out?

[Shrubbo]

Hey hannibal, first I am unsure of what you are posting there. The only line I had to change for the field FoV modification was in

 

\Config\View\View.lua

 

and that was .....

 

CameraViewAngleLimits[PlaneIndex.iKA_50] = {20.0, 120.0}

 

changed to...

 

CameraViewAngleLimits[PlaneIndex.iKA_50] = {170.0, 170.0}

 

It is set that way because I don't use zoom in or out, I just want a quick button press on game start to get my current favorite FoV. I have had up to 250 I think but it gets kinda funky on the peripherals as that res'.

 

Anyway to your questions, I don't know exactly what causes it but I do know what induces it or seems to at any rate.

 

If it is the same thing I get then I can tell you it is something to do with a 180 FoV, mine doesn't like that number at all. Chunks right up, sometimes it was a full seizure and other times I was able to sail straight through it.

[hannibal]

so basically when using triplehead 2 go, you just use trackIR on the X and Y axis...no looking up close or zooming out...

 

seems kind of limiting...at the moment, i am disconnecting th2g and seting up one 46"..

i am kind of bummed out on the fov, the overwheming demand of gpu push on the 8800gts that i have...i only tested on fsx and lomac.. performance isnt as cool as i expected...

 

i hope to re visited triplehead a gean in a few months..

right now i am trying to finish up with my saitek modified controller stack