Mailing List
Home
Forum Home
Softimage
Carrara
trueSpace
Dir3d-l
Maya - a powerful 3D animation and visual effects software
Macromedia Flash Development
Subjects
Cameras
scaleDown command
black out solved
Aircraft Tutorial
Mathematical XYZ ?
Its done This vs That
Its done first week
recommendations for screen video captures?
3DExplorer "Oddity "
New Director
ProTeam renewals
Fuel 's new websites (X post)
Blue peter create a make toy
targeting groups question
XPost: Shockwave 3D game ( sort of )
RES: RES: RES: Fish Modeling
Emitting particles from object intersection
Fuel 's new websites (X post)
Texturing
Big Break Contest Videos
New Plugins
Models and Texture on my updated site
Error Installing Patch tS6 6
Plasma?
Looking for Inspiration
Weird EMail Q
It 's done first week ?
Cherry not cranberry
New game
Camera Animation Problem
Particle plugins?
 
Python Scripting Problem

Python Scripting Problem

2004-04-16       - By Russ Andersson

 Back
Reply:     1     2  

I am looking for someone from Caligari to address this
issue, previously mailed to someone there to no
response. If you want to look at the scripts, drop me
a line through the website email.

Thanks,

Russ Andersson
http://www.ssontech.com

-- ---- --
I have been developing an export interface from our
camera tracking tool, SynthEyes, to trueSpace.  That
export path is working acceptably in general, though a
test user has encountered one particular problem that
I am writing about. I had actually seen something
similar earlier for a time, I think, as well.

Try executing each of the two attached scripts,
perhaps starting with bad1.py. After running it, hit
the "look through object" button to see the view
through the (already-selected) camera. Then scrub
through the shot and you'll see the Camera01Screen
object staying in view, relatively stable with some
minor size variation (and larger variation at the
end). Now try the same thing with the bad.py script,
and you'll see the Camera01Screen flying all around
wildly.

Yet, the only difference between the scripts are that
in bad1.py, all of the scn.Scale = (...) lines have
been removed, except for the first. (These lines are
used to make the screen track the varying zoom of the
camera.) So it seems that trueSpace is not setting
keys on the Camera01Screen scale correctly.

I would appreciate it if you or someone at Caligari
could please investigate this, and either suggest a
functioning workaround (such as a syntax or ordering
change),  or advise of a fix in trueSpace, so that I
may advise the users and prospective users. I would
greatly prefer to avoid having to include a disclaimer
in the SynthEyes/trueSpace export documentation & web
site.




__ ____ ____ ____ ____ ____ ______
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html