#CFIG386 3DS for PRO
43 messages in this thread
after reading the manual about trying to use animator pro, Im confused. i
have 32 megs of ram understand that i have to useCFIG386 3DS [D [D [D [D
command but not sure what physical addresses to use also the manual says to
use 2megs is that enough? any help on the correct command would be useful.
I hav have qemm386. thansk Rock,
You should be able to do a:
CFIG386 3DS.EXE -maxvcpi 30000000
That will reserve 2Mb for AA Pro.
– G
Thanks for the reply, I have run into a problem using my BCD 5000 and the
3dr2. I put vtr-device = vtpadi in the 3ds.set i use a targa+ and have the
render-device = rdpadi i have the set staset rdpadi = rdptplus1.exp and set
vtpadi = vtpbcd.exp the vtp and rdp files are in the correct path and the
proble is that when i try to intialize in the vtr setup box the COMPUTER
MONITOR scrambles on me and locks up the sytems. I have no problem
rendering scenes to the targa board and outside the 3ds2 program i can lay
images to tape via the bcd5000. Any suggestions as to what may cause the
scrambled computer screen. The video card is a speedstar and there is no
pass thru connetor. thanks in advance and although i just recieved my copy
i am awe struck Rock,
Rock… Have you added the device driver targap.sys with the following
switches in your config.sys file?
device=c:\tplus\targap.sys b0 md i220 d6 (assuming that your I/O address
for the frame buffer is at 0x200).
There's some additional info on setting the Targa+ tmode utilities on page
51 of the 3DSr2 install/performance manual. – Greg
My targa seems to work fine and I think i have narrowed the problem down to
the fact that if i set up the vtr setup menu before i do anything else
after entering the 3dshell then it will work,however when i try to load a
program from the load menu , nothing appears under the files. however i can
type in a file that i know exsists and it will appera
and i can render it using the vtr in 3r2. if i pull up a file first then
go to the vtr setup then the computer monitor scrambles and locks up. Did I
make myself clear (im confused). I've spent the last 7 hours working on
this. Rock
Rock. I know the feeling. I've spent the last two days getting a Targa 16
up and running correctly (the first problem with the RCPADI drivers was
fairly simple, Gary Yost and Kevin from CSA here helped me fix that one in
less than a day). The remainder of the time has been spent getting the
Diaquest controller to sync to the Targa 16 in composite mode. I've been
dropping frames (had some bad SMPTE code and had to restripe the tape) and
lastly the Sony VO-5850 deck has been making the edits ok, but the
animation frames have been coming out in monochrome. I've finally narrowed
down the problem. The signal coming directly off the T16 on the composite
preview monitor is rock steady, however when I put the VTR in the loop, the
signal ghosts very badly. (I should have noticed this from the beginning,
but I didn't). I either have a deck that is way out/off of signal specs or
b)there is so much RF in the room that it's causing the composite signal to
shift radically at the VTR. I'm going to check both signals (pre-VTR and
post VTR) coming from the T16 card this weekend with a borrowed waveform
monitor. I'll bet the post-VTR signal looks like garbage. Next step, I'm
going to try sheilding the deck by extending the cables and placing the
deck about 20' away from the CPU. If that does not work, it's back to the
repair shop for this VTR for signal realignment.
Regarding your lock up problem… I've worked with BCD contollers in the
past, but only using Topas. What it sounds like you're having is a conflict
between 3DS's VTRPADI exp driver and the BCD controller's TSR drivers. On
the Diaquest controllers, you can force their TSR to stay in base memory
(below 640) while the .exp (correct me I'm wrong here Gary) driver loads
high. See if you can force the BCD TSR to load low (on the BCD-500
controller an .exe file (5KECHO) loads the TSR, where in memory I don't
know. You might use QuarterDeck Manifest to see where it's residing.
Reboot, the machine and then start 3DS2 with your VTRPADI.exp loaded. Shell
to DOS and use Manifest to see where the VTRPADI.EXP is sitting in memory.
You'll probably find that it overlaps the BCD TSR.
(Continuation of the BCD/VTRPADI problem Rock Richardson is having).
Use QEMM to a) load the BCD TSR high (or force it low if you can) b) use
QEMM to exclude the area of ram that the BCD driver uses by setting it in
your config.sys statement.
Hope this helps… – Greg
Greg, I think you're probably correct in your analysis of Rock's problem.
It's most likely a memory conflict in low-RAM somewhere. QEMM to the
rescue again?
On another subject, I'm amazed that you're using a Targa16 to review our
renderer! It's very disappointing, actually. We put so much work into
making a beautiful true-color renderer, and you're using it with 15 bits of
color (only 32 shades of RG and B). ARGH… Isn't there any way
Truevision or another company will lend you a 24-bit card for at least the
duration of the review?
– G
Gary,
I agree with you that Greg L. using a Targa 16 is hardly fair to
your product. 3D Studio certainly does an excellent job displaying in
16-bit, but using the composite encoder directly off a Targa 16
(particularly if it's the older model dual-sandwich) is a shame. At least
the DQ-50P supplies sync.
Kevin Krell – Computer Support Associates
Gary… I think if Rock plays around with moving his BCD TSR's into high
memory (or low), it will end the memory conflict with the .exp drivers.
Yes, QEMM again! <g>
Regarding the Targa16… I * always * use an AT Vista hooked via RGB to my
21" Nanao multifreq monitor. The Targa16 was a sideline experiment to check
composite out (what actually set me on to this little jaunt was the ability
to set the renderer color depth buttons in the System Options pulldown
menu). Way, way back (before I had an RGB to NTSC encoder and was using –
ahem – Topas), the only board available was the T16. My first animations
(around 1987/88) were done using composite out and got sync directly from
the T16 in port. (As Kevin puts it: `composite isn't pretty'; especially at
these color depths).
I plan on giving 3DSr2 an extensive workout in many different
configurations. I've got the AT Vista, a Targa+64 and a Matrox MG-3D Ultra.
The Ultra should be interesting, as they have just released 24/32 bit
drivers for 3DS. I can generate models in AutoCADr11 using AME, shade them
and animate them in realtime, export them as a DXF or SLD file, then leave
the Acad shell directly back into 3DSr2 and import the pieces of the
overall model directly in for final texture mapping of the objects.
I've also tested with Hercules' Graphics Station cards and have been
playing around with the extra 8-bits of alpha using Ron Scott's Hi-Res QFX.
I've got some extra lead time on this piece and I'm savoring every strange
configuration I can dream up for your new release. (So far everything is
going swell… – except for my little problem with the T16 composite
experiment, which does work now). This, plus all the new goodies you've
packed in, is making this a great experience! – greg
Ah HAH! You're definitely set… I had no idea you were so well equipped!
– G
Thanx Gary. I just wanted to alleviate your fears that the software was not
going to be tested on anything other than a T16. Wouldn't do that. – Greg
Greg,
Do you find the drivers for the Hercules Graphic Station a bit
disappointing? Everyone I've spoken to says they'll only do 16-bit,
regardless of Hercules' having promised 24-bit drivers would be provided.
Kevin Krell – Computer Support Associates
Greg,
I'm under the impression that PharLapp loads the .EXP drivers, so they could
be anywhere. Should *not* be a conflict with the driver *location*, but
there might be one due so *side effects* of the driver.
Ken ///
Greg, we've used a TARGA 16, Diaquest, *and* the VO-5850 deck for earlier
animations. The results were surprisingly good. One thing to check is
that you are **NOT** using both the RGB and Composite signals out of the
Targa 16 at the same time. The signal strength from the TARGA 16 will NOT
allow this.
We still use the Diaquest and VO-5850, but have upgraded to a TARGA 64+.
Next step is a PVW-2800……
-Jeff
Jeff,
Of course with the PVW-2800, you'll have to go with a DQ422
(serial).
Kevin Krell – Computer Support Associates
I'm hoping to find a software controller that will work, instead of another
Diaquest board. Any recommendations?
-Jeff
Jeff,
I'd go with the Diaquest, but you could look into the following
software controllers to see if they'll support the deck:
Chase Technologies – SoftVTR
International Coprorate Video Inc. – Animaster 415/426-8230
Kevin Krell – Computer Support Associates
Gee, I didn't know line noise could *TRANSPOSE* characters. Remeber, the
Diaquest hardware has pretty well proven its reliability and industry-wide
support, at a cost of $2380, versus the software-only approaches (usually
less capable, for instance ability to grab images) for $995. While I'm
sure many would not view the $1400 difference as minor, I feel that it is.
Kevin Krell – Computer Support Associates
Wow Jeff… You just proved my point. There really * are * real-life
configurations that I'm trying to test out. (I take it that you used
composite directly off the T16 for your animations?)
You've got me on the PVW-2800… My feeble memory fails me. – Greg
Yup, my partner had the TARGA 16 for a few years already…..we got 3DS,
purchased a used 5850/5800 suite from the local university, added a
Diaquest, and……we were doing cheap animations for industrial level
work.
Word of mouth kept us busy enough that we've been able to add two 486's a
TARGA 64 and a few other goodies……enough to interest the local TV
stations……now we just haul a portable 386 w/TARGA 64 to the studio and
dump onto their 1". We don't have a controller to run their deck, but the
sequences are usually only 2 seconds or so (60 frames), so we've written a
batch file to load the saved TGA files to the frame buffer and wait until
we hit the "any" key, before loading the next. While the particular frame
is loaded, the deck operator just hits their edit key. Do this 60 times
and it's done! Cheap, effective, and not too time consuming. They get the
quality they need and we…..get paid!
-Jeff
P.S. the SONY PVW-2800 is an entry level BetaCAM SP without all the bells
and whistles of the more expensive models. Apparently the recording
quality and transport is quite comparable to the expensive units.
Portable animation… Bring the whole shabang right to the studio's 1". I
like that idea!
BTW: I seem to remember seeing a msg a few posts back about the PVW-2800
having problems with head clogs, mechanism problems when you beat on it for
single frame edits. Might be worth looking into before you expend the
dollars (I personally don't have any experience with that deck). – greg
Yes, I just read through that thread about the reported problems with the
PVW2800. One guy swears against them, while another says that after the
no-charge upgrades they've been excellent, so……I guess we'll hold on a
bit longer to see some further reports.
-Jeff
Be carefull about the PVW series their have been alot of prolbems with
them! Sony has been doing upgrades to them, they are having prolbems with
head clogging, jammed tapes, ect. If you like I can upload a message thread
from the BP forum disscusing these prolbems. Let me know.
Regards
Steve
Thanks Steve! I'd appreciate seeing that thread…..I should get over
there more often!
Please upload the thread here, or to me via email if you prefer.
Thanks!
-Jeff
P.S. are the upgraded units considered "fixed"?
Jeff, Here is the message thread. I tried to upload this earlier, but I am
having trouble with the "/split" command in Tapcis, so I will try again, and
if it does not work I will upload it in parts to you.
Regards
Steve
[Continued]
[More]
Thanks, I will try to play with it somemore. It seems that the better the
software gets the more equiptment that you need and the more problems you
have with conflicts. Such a vicious circle. Hope you get everything sync.
together soon. So far The BCD ADI is the only major problem i've run into
and usuallly if it can go bad it will with me so i consider myself lucky.
Good luck Rock
Rock… Please let us know how you fare with the BCD ADI conflicts. Hope
some of the suggestions helped. Good Luck. – Greg
Rock-
I havn't installed the ship version of R2 yet so I don't know if the
dissappearing files have been fixed or not. Apparently not if your having
trouble with them. Bob Howard and I both informed John S. at ADesk of the
problem and he was looking into it. However, the workaround I've come up
with is to initialize the VTR (This seems to be what makes the files
dissappear) and then shell out to Dos and reenter R2. Voila, the files are
back and you can pick them.
-Mark
Mark, I used qemm and re-intialized with the new drivers and although its
still not perfect the screen doesnt scramble if i load a file first, but
when i l wwent to load a file after intializing the bcd adi the mesh
directory listed about30 files all with the same name. when i triedto
load one of them then the system crashed. I quite and went back to the
tutorials, almost through them and its a lot more fun doing the tutorials
than running down confi problems. Let me know if your haveing the same
problem with the latest version. Rock,
Rock- I'll let you know as soon as I have time to load up the shipping
version. I know I have that problem now with the beta release I've been
using. Have you tried to shell out to Dos and then reenter R2? That seems
to bring the correct file names up and everything seem to work OK. Let me
know.
-Mark
Rock, I want to reitterate that this is a BCD DRIVER problem, not a problem
with the 3DS code. You're going to have to get the BCD people to fix it,
unfortunately.
– G
I understand and I am working in that direction. The BCD people seem very
anxious to work it out and I'm sure that it will be done. On a nother note
I have just finished the tuturiols and am truly amazed at all the new
gadgets at my disposal. I have been working with the noise.sxp and have
applied it to a large flat rectangle which i spin on its center. the camera
is located just below the rectangel to give the impression of the sky
moving overhead very fast. the Noise images seems to give me diffenent
lines of contrast almost like waves. I thought that the noise.sxp would
give random patterns. Would animating the Noise.sxp change the liner
patterns? I am sure your tired of hearing about how great your upgrade is
but fact is fact Thanks, Rock
I'm glad you're staying on top of the BCD people. It really isn't that
hard to write a driver that works correctly, so it shouldn't be long.
Regarding noise.sxp… the sample version of noise.sxp that ships with
3DSr2 has a "periodic" component to it. We've recently finished a
completely random version that will be included in a collection of IPAS SXP
files that I hope will be available by mid-to-late summertime.
Great news that you're having fun with the new tutorials. Enjoy!
– G
Rock,
I hope you will change your setup to SET RDPADI=RDPTPLUS.EXP (note
your message had a 9-character filename + the extension.
Kevin Krell – Computer Support Associates
my spelling may be off but the setup is exact.(refere to previous thread)
Rock
Your message was very hard to read.
I think you said that you've got a set statement that reads:
set staset rdpadi = rdptplus1.exp
That's not going to work for a number of reasons, including the wrong set
statement and a nine-character .exp filename.
Beyond that, if you have specific questions about the bcd adi driver (or
any adi driver, for that matter), you're going to have to go directly to
the manufacturer for support. I don't have one of those controllers and
have no idea how to help you with it.
– G
i have been on the phone for most of the day with BCD and they are checking
it out. they did mention that you guys called about a problem about file
not showing up (meshes) but thought that the problem was taken care of.
(refer to my previous thread) Rock
I don't understand what you mean by the sentence:
"they did mention that you guys called about a problem about file not
showing up (meshes) but thought that the problem was taken care of."
I have never called the BCD people. I understand your frustration, but I
know very little about specific controllers and can't help you much. (I
wish I could.) Greg's suggestion to use QEMM to move your display memory
HIGH is a very good one.
Rock, let me tell you how we implemented the VTPADI interface for VTR
controllers within 3D Studio. First, we took all the functionality that
was in our internal Diaquest interface and we broke that out into a new ADI
type. Then, as a test, we used the Diaquest VTPADI driver that works with
Animator Pro's FLITAPE as an example. Once we got the VTPADI interface
working perfectly with the Diaquest VTPADI driver, we knew we had a working
interface. At that point, we sent out betas to the various VTR controller
companies. To be perfectly honest, since these companies had never written
ADI drivers before, they've been floundering around a little. I expect
it'll take them a little while longer to get it right. But that's THEIR
problem, not ours. That's why we went to the trouble to get the VTPADI
interface right. If I had to worry about DRIVERS, I'd never be able to
sleep at night.
– G
I understand your position. and dont get me wrong i think that the program
is great but i thaought youd be interested in learning about specific
problems so that IF they can be corrected they will be. If its entirely a
porblem with the BCD people then maybe you guys can work together to fix
it. I can certainly live with it like it is. I just endered 420 frame. I
just added the CD rom (works perfectly) the arga+ (works perfectly). Thats
a milestone for me to have everything work correctly on the first try. I'll
check the low memor conflcit (which will probably fix it) thanks again on a
supurb product Rock
Gary, regarding ADI drivers for controllers… Maybe there's another driver
product `lurking' in the wings here from Jake Richter's company, Panacea.
Eh? – greg