• News
    • General
    • Software
    • Industry
    • Video Games
    • Tech
    • Hardware
  • Articles
    • General
    • Reviews
    • Interviews
  • Tutorials
    • By subject
    • By software
    • Training & Courses
  • Resources
  • Spotlight
    • Reels
    • Films
    • Film Trailers
    • Game Trailers and Art
    • Breakdowns
    • Making Ofs
    • Music Videos
    • CG Videos
    • Images
    • Spots
  • Contribute News
News Channels:
  • CG News
  • 3DS Max
  • Blender
  • After Effects
  • Modo

Software > 3DS Max > Scripts

SoulburnScripts Updated

Oct 14, 2009 by CGP Staff
0 |
Tweet
New script: uVTransfer: transfers uvs from one object to the next. Useful if you have two identical meshes, but their vertex order is messed up (like perhaps in the situation where you exported the object to a seperate application for uving and that application messed up the vertex order). Plus updated several older scripts. Read on for more. New script: uVTransfer: transfers uvs from one object to the next. Useful if you have two identical meshes, but their vertex order is messed up (like perhaps in the situation where you exported the object to a seperate application for uving and that application messed up the vertex order.) This script can transfer the uvs from the new object to your original object in max, even if the order is different. This script may still be a little rough, so make sure to save your scene before you use it, and if you find any models it doesn’t work on, let me know so I can try and fix it.

Updated several older scripts, here’s the major updates:
imagePlaneMaker: Fixed a bug that shows up if you have max set to use Real World Scale by default.
mirrorObjectAlongAxis: There is a maxscript bug where using the maxOps.CloneNodes function (which this script does) causes not only the objects to be instanced, but their transform controller as well, but only if you’re cloning a hierarchy. So if you have say a sphere linked to a dummy, and run the script, then move your sphere, the second sphere will move as well. Hopefully autodesk will fix this bug in a new release, but until then, I added the “Uninstance Transform Controllers?” checkbox. This will uninstance the transform controllers. However, this workaround has the side effect that if you actually meant to have the controllers instanced, it will uninstance them, since the script can’t tell whether you meant to have them instanced, or whether they were just instanced due to the maxscript bug.

http://www.neilblevins.com/soulburnscripts/soulburnscripts.htm

Source: Neil Blevins

Related News

  • SoulburnScripts Updated Dec 2nd 2009
  • SoulburnScripts Updated July 2nd 2009
  • SoulburnScripts Updated

ADVERTISEMENT

Latest Comments

  • Artur Mandas on V-Ray now officially available for Blender
  • Jumanji on V-Ray now officially available for Blender
  • slebed on V-Ray now officially available for Blender
  • Dan on V-Ray now officially available for Blender
  • CGPress Staff on V-Ray now officially available for Blender
  • JokerMartini on V-Ray now officially available for Blender
  • Nossgrr on Autodesk releases 3ds Max 2026.1 with a new Attribute Transfer modifier
  • mohinder on V-Ray now officially available for Blender

Latest Features

1

Review of the Huion Kamvas 13 Pen Display for 3D artists

6

Archvis artists – what the hell do they do?

See All CGPress Features

Follow CGPress

Terms and Conditions | Privacy Policy | Cookie Policy
Copyright ©2000-2025 CGPress. All rights reserved.

About Us | Contact Us | Contribute News | Advertise
facebook
twitter
rss
Manage Cookie Consent

CGPress uses technology like cookies to analyse the number of visitors to our site and how it is navigated. We DO NOT sell or profit from your data beyond displaying inconspicuous adverts relevant to CG artists. It'd really help us out if you could accept the cookies, but of course we appreciate your choice not to share data. 

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}