#Targa+ config? (Arrrgh!)
16 messages in this thread
I'm having a heck of a time getting my Targa+64 board to work. One problem is
that I've never seen a Targa board work, and I really don't know what to expect
from it, i.e. it's hard to trouble shoot if you don't know what to look for.
I'm downloading the new march 95 vibrant drivers from the forum tonight, so
I'll give them a try tomorrow.
Here is my question: I'll configure the vibcfg to use the vibrant drivers set
to the targa+ in the rendering output option. Will I then see the additional
frame buffer button in the materials editor? How will I output flics to the
t+?
I've gotten the tconfig live setup to cause my Sony 1311 multisync monitor to
switch between different settings so I know there is some communication going
on. And I've gotten 3DS to load with the rdpadi device driver. But I can't
seem to get any image on the ntsc monitor.
Should I be seeing a flickering blue screen, or a stable grey screen on my 1311
Sony NTSC monitor.
I've excluded E000-EFFF from mem in my Autoexec.bat file, and used this address
for the T+. How will I know if I've got a memory conflict?
Any suggestions would be much appreciated!!
Carlton
I've lost about 2 days on this one, not to mention my sanity and self respect.
(G)
>> I've excluded E000-EFFF from mem in my Autoexec.bat file, and used this
address for the T+. <<
I assume you meant your config.sys file? <g> Here's my relavent
config.sys info:
DEVICE=C:\QEMM\QEMM386.SYS RAM X=E000-EFFF RF
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\TPLUS\TARGAP.SYS B0 I230 ME R1 W1
And in my autoexec.bat:
PATH=C:\TPLUS; (etc.)
set RDPADI=c:\3ds4\drivers\rdptplus.exp
TMODE 11 6
TPCLR
"Tpclr" will clear the framebuffer, and give you a blue screen.
Otherwise, you'll have the last rendered image sent to the framebuffer showing,
or a really annoying speckled flicker if you've rebooted. "Tmode 11 6" puts
you at 512x486x1.266, without having to run tconfig.
Is 3DS locking up, or are you just noot seeing anything? I've had
conflicts with the Targa and other drivers, try the ol' vanilla boot, adding
stuff in one at a time. I've also had better luck using the rdpadi setup,
rather than choosing the Targa+ drivers in 3ds vibcfg.
Hope this helps,
Paul S.
Thanks for the reply Paul.
I'm on my way back to work now and I'll give your suggestions a try.
When I boot up with my NTSC monitor powered on I can hear it sync up with the
targa board as the computer loads its startup configuration, 3DS loads fine and
runs OK. In the materials editor I see that the render frambuffer button has
come up as an option, but when I use it the "image rendering" message appears
for a second or two and then…nothing appears in the monitor.
I'm real green at this, for all I know I've not set or switched correctly any
of the 6 or 8 options, for instance it took me a while to realize my monitor
had 4 possible input selections. (g)
Am I correct in assuming that if I use a nine pin RGB input into my monitor,
that it doesn't matter if I've set the output mode switches on the Targa+ to
component or composite? Any ideas if I should set my monitor to digital or
analog in?
When you use this boot up config you sent me and you turn your T+ monitor on,
what do you see? A jerking, jiggling blue screen, a stable blue screen, or a
stable grey screen?
If you choose to play a flic on the frame buffer monitor to output to tape, how
do you set 3DS up to do it?
I'll let you know how it goes.
Thanks again,
Carlton
Carlton,
The Targa+ output is analog RGB. Does the monitor work down to a
15.75kHz horizontal scan rate? If not, then make sure your Targa+ mode is set
to a non-interlaced mode (compatible with VGA frequencies). Best bet is to use
the RDPADI for still renders (do VIBCFG for your VGA if you want to render to
VGA using Vibrant drivers, then you can change to RDPADI in Render Config. at
will). You can set VIBCFG to use the Targa+ driver for flics.
Kevin Krell – Computer Support Associates
Kevin,
Do you know of anyone who still makes a good long persistence monitor at 15.75
hz scan rate? The last one I know of died with Mitsubishi Diamond scan.
John
John,
I think Electrohome still makes a long-persistence phosphor monitor with
the right specs. Barring that, I've got a demo Mitsubishi 3425L9ATK (14")
that's just been sitting in my supply room since we had replaced with a Mit.
20".
Kevin Krell – Computer Support Associates
>> that's just been sitting in my supply room… <<
Kevin,
Thanks for the offer. I think I'm pretty well set with the present way of doing
things but I kinda wondered as I spent some good years with that type of
monitor setup and it saved my eyesight, I'm pretty convinced. These low
emission high scan rate monitors seem to be just as good, if not better, and
more accurate color wise, but I kinda liked the softer look / glow of the long
persistence models. If Mitsubishi still makes a 20" at that scan rate, I might
consider that with current low emission technology a viable solution sometime
in the foreseeable future, if and when I can convince Matrox to come out with
an NT driver. They are definitely coming out with one for 3DS, but I'd like a
display driver so I can paint. I'd forgotten about the Electrohomes. I never
cared that much for them because the resolution seemed low with perceptible
gaps between the scan lines. But maybe that's changed.
John
John,
My distributor still lists a Mitsubishi HC3925L9E (TK, I think) that is
the lower scan rate, with the L indicating Long Persistence.
Kevin Krell – Computer Support Associates
Thanks Kevin,
That's good news, I'll add it to the list. I'll just have to see how it goes
with the driver situation. I'm still pushing for it, in spite of the uproareous
laughter. <g>
John
Thanks Kevin –
I've got the Vibrant drivers to run the flics from within 3DS out to my monitor
and video tape deck. That was exciting?
I'm still struggling with the Materials Editor though, its currently configured
with the Vibrant driver too, but the NTSC monitor shows a band of snow about
mid-screen. I'm not running QEMM but I think I've rem'd about every possible
variable out of my startup files.
Next will be to get the flics to play out of RAM. Is that possible from within
3DS or do I have to use flitape in Anipro?
Carlton
" Will I then see the additional frame buffer button in the materials editor?"
You can configure for the Targa with the Vibrant graphics driver, or you can
still find the RDPADI of use – the Materials Editor's thumbnails will not
display on the NTSC monitor (you have a TV monitor running with this setup?) if
you use the Vibrant Targa driver.
"Next will be to get the flics to play out of RAM. Is that possible from
within 3DS or do I have to use flitape in Anipro?" If you need FLITAPE it's to
output flics frame by frame that need to have 30 frames per second. This will
be helpful with animations that don't play properly on the computer high
resolution architectural walkthroughs come to mind).
To play out of RAM, get the Targa drivers to run AAPro and the player on the
NTSC monitor.
Thanks Nik
I think I got it:
The Vibrant Targa drivers won't display the Material Editor's thumbnails on the
NTSC monitor's screen. I'll need to use the RDPAADI driver that shipped with
3DS.
To play flics out of RAM I need to configure the Targa to play the Anipro
player.
Is this described in the manual's? I've only found reference to the flitape
configuration.
Flitape is only for single frame recording output.
Sound correct to you?
Carlton
Carlton,
The Targa+ board comes with an Animator Pro driver (probably ends in
DRV) that goes in the directory with the other AAPRO drivers. If you
initialize the Targa+ and set a resolution (say, 640x480x16-bit), then AAPRO's
Set Screen menu will let you select Interlaced, Int. Live (overlay), & Non-int.
at that res. There is also a POCO utility to set other features of the board,
including the overlay color.
Kevin Krell – Computer Support Associates
Kevin
<That was exciting?>
Should have read: <That was exciting!>
VBG
Carlton
Well Paul I took your message and the new Vibrant drivers back to work and
fiddled all afternoon. Right now I'm playing flics on the NTSC monitor from
within 3DS, but the Materials Editor is still giving me problems. I've
configured the M.E. to dual display with the Vibrant drivers and two things
happen: screen cursor movement causes a ghosting effect where nearby parts of
the M.E. interface appear to show through, and the NTSC display monitor renders
with a band of active snow about mid screen.
I tried your setup without success – I'll try it again tomorrow. I'm not
running QEMM, and the whole memory management issue still escapes me. (Each
time I think I understand it something stops working VBG)
Any ideas how to play flics from RAM memory in 3DS? I'd like to output about
150 Megs worth onto video tape without such obvious tearing.
I have Anipro but have never used it except for the browser and the flic
player.
Carlton
>> I've configured the M.E. to dual display with the Vibrant drivers and two
things happen: screen cursor movement causes a ghosting effect where nearby
parts of the M.E. interface appear to show through, and the NTSC display
monitor renders with a band of active snow about mid screen. <<
I get the same cursor ghosting when I use the Targa+ drivers for AniPro.
If/when I use the Targa+ for the ME, I select the framebuffer button, and just
get the little squares with the test spheres/boxes rendered on my NTSC monitor,
I don't get the entire ME. Are you running your Targa+ as a single screen
setup? I've never attempted that.
>> I'm not running QEMM, and the whole memory management issue still escapes
me. <<
I know what you mean. <g> You definitely need one though, I assume you
are using EMM386?
>> I'd like to output about 150 Megs worth onto video tape without such obvious
tearing. <<
I believe AniPro loads flics into RAM…? I've had pretty good luck going
straight to tape that way, though not at 30 fps. Otherwise, Nik answered most
of your questions. If you need to, I could put your flic to my PAR and output
at whatever frame rate you need. Write e-mail if interested.
Paul S.