#Browser Problems
20 messages in this thread
Have had problems getting browser to work on several machines.
Seems to like the vibrant update on disk 7.
Only works well with the texture universe cd. Have tried 2-3 others.
Beyond that, several questions:
1) With non-indexed cd's like "World-creating toolkit", documentation
suggests creating an index saved to local drive. I've tried that but
the darn thing makes an index of the local drive.
2) Slideshow doesn't funtion & view image is 15-20 times slower than
'Render/View/Image'
3) All tga's on cd-rom show up as blank squares with an x. What's the point if
you can't see it?
Rick,
To create a non-resident index file:
1. Use browse (next to SINGLE) to select a search path on your (non TU) CD-ROM.
2. select DO SEARCH. You should get a window with a series of X's in the
graphics display.
3. Select Build index. Make sure the path you select is the same as the path in
the Search Path(s) window.
4. Press OK, it will prompt you "Can't create index file". Select Continue. It
should then prompt you "Would you liketo create a non-resident index file?"
Select OK.
5. TU should then build the index, for the drive on your CD-ROM, placingit in a
local drive.
6. Select Do Search, and you should now have images in the Window.
As for your delay in viewing the image, do you have a Targa card AND a VGA
card?
-Brian
Brian,
Have a targa + 64 board and an ati wonder plus board.
not using pass-thru.
BTW Just found out that targa plus 64 isn't well liked for "disk to vtr"
today from the readme.doc. Re-read it today. Anyway around the split buffer?
Pulled out my hair for a while when I thought my soft-vtr was dropping frames.
Rick
Hi rick,
I'm curious about disk to vtr "not liking" the T64+. I don't seem to recall any
problems w/ the 64+. It should work at 512×486 at 32 bits just fine. Could you
go into more details.
About TGAs on the CD appearing with X thru them maybe it is because these
images don't have a preview proxy, a small postage stamp of the actual image.
Earlier versions of 3DS had problems dealing with targa files that used version
2 of the TGA file spec.
Robert,
>///
I'm curious about disk to vtr "not liking" the T64+. I don't seem to recall any
problems w/ the 64+. It should work at 512×486 at 32 bits just fine. Could you
go into more details.
<\\\
I just started having problems with mine, worked it out by getting the new
drivers from s-vtr, and truevision, & using vitc instead of longitudinal time
code. I just recently noticed the message about the double buffer on the targa
+ in the rel 3 readme file. What happened was that a blank frame was
intermittantly being put to tape tape leading me to believe that the s-vtr was
dropping frames. When I went & used the s-vtr program to lay single frames, it
worked like a charm. It did stop several times with a message that the serial
control was not connected.
I have a perfectly good soundblaster board which I can't use in my
animation-out machine because it conflicts horribly with the targa + board.
Even using multiple boot senarios didn't work. Multimedia isn't quite here
yet. Unless you buy a proprietary box which costs three times retail to get
suped-up.
ONE QUESTION: Is there a utility to check all my targas before I attempt to
send them to tape? I hate having a taping interrupted by a corrupted file.
Rick
>>I have a perfectly good soundblaster board which I can't use in my
>>animation-out machine because it conflicts horribly with the targa +
>>board.
I've got a SoundBlaster 16/ASP board and a Targa+64 in my machine (Gateway
P5-60) with no problem (other than they eat up memory with drivers/page
frames). Have you just run out of I/O addresses/IRQ's, etc or what's the
problem?
Dave
Dave,
>///
I've got a SoundBlaster 16/ASP board and a Targa+64 in my machine (Gateway
P5-60) with no problem (other than they eat up memory with drivers/page
frames). Have you just run out of I/O addresses/IRQ's, etc or what's the
problem?
>\\\
They both want to sit in the same place, & don't like each other.
RIck
Rick,
Generally, the only problem with SoundBlasters in with Targas is to make
sure the I/O address is at least 20 away. Thus, if the SoundBlaster is at
220H, set teh Targa for an I/O address of 240H.
Kevin Krell – Computer Support Associates
KEvin,
the sound blaster won't work at 220 & the targa won't work at anything other
than 240.
Rick
Rick,
Take Robert Seiwart's advice on setup of the SoundBlaster & Targa+. Many
people are using both boards successfully – it's usually just a matter of
getting those I/O addresses set (the Targa+ can work at a variety of addresses
– in fact, you can fill a whole computer with multiple boards, displaying
different images on each).
Kevin Krell – Computer Support Associates
Kevin,
I'll try it. Is there a decent utility to monitor the conflicts? I
had a tough time installing the targa+ the first time.
Really hate to fix what'ws not broke.
Rick
The double buffering on the Targa+ doesn't kick in unless you tell it to. If
you run tdemo.exe you will see images blending very nicely from one to the
next. That is what you can do with double buffering and the internal linear
keyer. 3DS never invokes the second buffer. I don't think this is your problem.
maybe a loss of timecode or something else. I remember the early JVC BR-822Us
had serious missed frame problems. I don't know what you are running.
As for getting the sound blaster to work with the targa, I also have that
working without any problems. Your problem there is that the default IO addr
for both the targa+ and the SB are 220. What I do since some sound software is
hardcoded is change the IO addr on the targa+ to 200. RTFM for the proper
switch settings and also modify the targap.sys line in your config.sys to show
the new io addr for the targa+. All other programs (SVTR and 3DS) will pickup
on this automatically.
To check my targa files (on the targa+) I use gettga and ls. gettga came with
the targa+. It reads a single image up onto the screen. ls is a utility I wrote
with generates batch files. If you have norton utils you can use ff to also
generate a batch file to preview your images.
Good luck and i hope you resolve your SB, SVTR, T64+ problems without to many
headaches. Chaos.
>> The double buffering on the Targa+ doesn't kick in unless you tell it
>> to
PMJI, but you should look again at the README file that shipped with 3DS. It
-DOES- indicate a problem with the Targa 64+ actually recording black frames
rather than the intended image in some cases. If you'd like, I can dig it up
and post that paragraph here. I believe the recommended solution is to use the
Diaquest TPLUSLOA.EXE to load your frame and Diaquest (or something similar) to
control the recording deck.
In my personal experience, I have VERY rarely had any trouble whatsoever using
the standard disk-to-tape operations (FWIW).
– Dave
BTW, I am interested in obtaining a copy of the demo tape you were showing at
the 3DS Users' Group meeting. Is it generally available to the public?
I don't know about the tape. I'll have to cal Tina and ask. If so I'll have a
few at the next user's group; unless someone sponsers me to Siggraph.
>> I don't know about the tape.
Oh well. I'm always looking for inspirational material. It reminds me how
much further I should be pushing 3DS. <g>
Brian explained how to index a CD-ROM with TU very well. Re your viewing image
problem (slowness), it's due to your using TU in an 8-bit mode, and it's
intended to be used in a hicolor (15/16/24-bit) mode instead from the Materials
Editor. When used that way, the view image function is instantaneous.
– G
Gary,
Brian's explanation was right on the money. Re slowiness, why isn't
browser 15/16/24 bit? I'm back to hunt & peck in the materials editor. It
would be nice to view the selected ones quickly Wasn't that the point of
browser? Why is it 8 bit?
RIck
You misinterpreted what I told you. Since Medit is supposed to run in a
hicolor mode (15/16/24-bit), the Texture Universe Browser was also optimized to
run in this mode. If you do happen to run TU in an 8-bit mode (ie, from the
Ed/Kf), you'll take a performance hit.
– G
G
I guess it matters where you are standing. It works fast in the medit?
Rick
It does if Medit is running in a hicolor mode.
– G