#set=FILE config problem?
12 messages in this thread
To AutoDesk, Yost group, Vibrant and all,
We've ran into a simple problem: we're trying to run 3DS R4 with most files
installed on a network with two different configurations. The 3DS.SET file is
pointing to local directories on each PC.
We've run this on twenty PCs running 3D Studio simultaneously without a hitch,
but all those PCs had the same video configuration. We now have an additional
twenty stations we wuld like to run from the same setup, but they have a
different video card configuration.
Using a different file (3ds set=m32.set) to start 3D Studio doesn't work. if
we copy the m32.set to 3DS.set, it works just fine on the new PCs.
It seems that vibrant is misreading something. If stops with an error
"configured graphics file not found".
Is thereanyone who has any idea of what we can try? We can't get past the
vibrant error. We can't have multiple setups with multiple 3DS files?
Mark K.
Brian Rudolph is the resident net rendering expert, and Nik Grant is the local
display card expert. I'm sure that they'll see your message on Monday.
– G
<<Using a different file (3ds set=m32.set) to start 3D Studio doesn't work. if
we copy the m32.set to 3DS.set, it works just fine on the new PCs.
It seems that vibrant is misreading something. If stops with an error
"configured graphics file not found".>>
mark,
Just copying the 3DS.SET file is not enough. What you will have to do is run
"3ds vibcfg" on one of the systems that has the new video cards. Configure the
cards, and run the video test mode. Make sure that works. Once that one machine
is working, you can then copy the 3ds.set file from that machine to all the
machines that have the exact same configuration.
-Brian
Brian,
Thanks for the reply.
I have configured the one setup for the new cards, and I did get a 3DS.SET that
would work with the new PCs. (this is 3DS running in a network server
directory) Now the new machines work just fine with the new 3DS.SET.
I took this new and properly configured 3DS.SET and renamed it M64.SET, and put
back the old 3DS.SET. I still can't use the new configuration when I run 3DS
set=m64.set . I get a vibrant configuration error. The old PCs seem to be
running fine with the old 3DS.SET back in, but for the life of me I can't get
the new PCs to run with the set=m64.set.
Can this work? or is there something I am missing here?
Mark K.
mark,
<< took this new and properly configured 3DS.SET and renamed it M64.SET, and
put back the old 3DS.SET.>>
Why?
Why not just have the proper 3DS.SET file for each machine be on each machine?
I'm missing someting here. Could you explain why you need to use the set=
statement again.
-Brian
Brian,
Sorry for not getting back to you earlier.It's been a crazy week…I managed to
find the problem. Thank you all for responding.
>>Why not just have the proper 3DS.SET file for each machine be on each
>>machine? Could you explain why you need the set= statement again.
Good question. I am running all my copies of 3D Studio R4 from the network.
There IS no local 3D Studio installed anywhere in the labs. That is why I need
different SET files with configs. I have 37 3DSR4 locks, and 72 PCs on this
network with different combinations.
So as you can see, we have to use different set files for the different
configurations we have here. Basically we have four different types of
graphics cards: ATI VGA Wonder XL, ATI Turbo VLB (Mach 32), ATI Graphics
expression (Mach 64), and the Matrox Impression+.
The default setting is the ATI VGA Wonder XL, and that is what the 3DS.SET is
configured for.
The other ATI cards both work with the Mach 32 vibrant configuration, and this
is in a file called M64.SET.
I'm building a third SET file with the Matrox config.
My original problem: I could not get 3D Studio running with 3DS set=M64.set on
the appropriate machines. After some digging, I found out why: The batch file
parameters was passing the lines wrong. For example, if you type:
3DS set=M64.set
at the command line and 3DS.BAT file responds, you will find that this is what
the batch file sees:
3DS set M64.set
No wonder it never worked. Even typing in "3DS set=M64.set vibcfg" wouldn't
work, as 3DS got "3DS set M64.set vibcfg" through the batch file.
After a lot of "if !%1!=="set" goto…" statements in the batch file we got it
working just fine.
I've since improved the system: now we have a DOS environment variable in each
PC that sets the station number and config to use, and the whole thing is
purring along.
I have some issues to raise regarding Network rendering and a wishlist request,
but that's for another time.
Thanks again, Brian.
Mark K.
CAD Program Coordinator
Sheridan College, Brampton, Ontario
CAD/CAM Institute ATC, MMATC.
The SET=M64.SET should work for you. I have a TEXTUNIV.SET which I use
occasionally, and I just tried it now successfully.
Make sure that if you rename the M64.SET to 3DS.SET that it works. It might
not, which would help narrow down the problem.
If it does work, then you might be running low on the environment space for the
SET statement. Are you running a batch file? What are the exact steps you do?
Are all the .SET files in the 3DS4 directory?
Nik,
Thanks for your reply. It turned out to be a problem with the way DOS
interprets the "=" sign in a batch file. The "=" is dropped…..
Maybe this could be wishlist requirement: maybe change the command line
parameters for a future 3D Studio. I'd suggest something more along the lines
of a unix "switch" thing:
3DS -s M64.set
That way, there's no characters that get dropped by dos or unix in case of a
batch file or a script file, respectively.
This could be improved a little further: just make some environment variables
that could carry this info, similar to what AutoCAD does.
For example, I would suggest two things:
– Use a variable to find an alternate "SET" thing. This would be the default
that could be overridden by the switches on the command line. For example:
set 3DSCFG=D:\3ds4\Config1\M64.SET
An advantage: the SET file could then be anywhere on the system.
– Use a variable to point to a directory where it can find the 3DSNET.SET file.
For example:
set 3DSNET=D:\NET
This would work quite well, and will avoid the problem of having 3D Studio
loaded on EVERY machine you want to use for rendering. What if you want to run
3DS for Network rendering from a common network installation? Curently, you
have to run it locally in order for it to have a different 3dsnet.set file for
each machine. A royal pain.
I'd appreciate knowing if this is something that makes sense, or it is just me
going around the bend? I'd love to hear from you and Brian and anyone else on
this matter.
Mark K.
Please see my reply to Brian Rudolph on this.
Mark,
I've passed on your comments to Jonas, who is the keeper of the wishlist. This
seems logical to me, although with the development directed towards a future
version on NT, I don't know enough to know if this is excellent feedback or not
applicable.
Your explanation seems clear. Thanks.
Maan:
Sounds like you have the batch file to start 3DS licked! Have you considered
posting your findings with a short README to the libraries here to help others
starting out? TIA!
Greg Pyros
Gregory,
Will do. Hopefully when things are a little quieter next week, I shall post
the trials I went through to get 3DS running from a central location off the
network…
It didn't go exactly as planned, but it works ok….
Mark K.
>>It turned out to be a problem with the way DOS interprets the "=" sign in a
batch file. The "=" is dropped…..
Sorry if I'm hopping in on this one a bit late, but I use the
"set=…" statement from batch files all the time to start 3ds in
different display color depths, and it works perfectly. DOS (at least
on our machines) sees the "=" in batch files just fine. I don't have
any suggestions as to why your systems won't accept the commands, but
I'm curious, do your machines see the "path=…" or "set
temp(etc)=…" lines in the autoexec.bat? (which is of course just a
batch file itself)
David