Community
3ds Max Forum
Welcome to Autodesk’s 3ds Max Forums. Share your knowledge, ask questions, and explore popular 3ds Max topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Potential Issues caused by third party MaxScript files - ALC and CRP

74 REPLIES 74
SOLVED
Reply
Message 1 of 75
Alfred.DeFlaminis
52791 Views, 74 Replies

Potential Issues caused by third party MaxScript files - ALC and CRP

Hello all,

 

Recently there have been some scattered reports of some issues which have been traced back to two third party MaxScripts.  Autodesk has investigated these issues and two articles have been created about this which I wanted to share here. If you are having any issues, please refer to these articles below:

 

ALC MaxScript article:

A 3rd-party MAXScript (hereafter called "ALC"), can accidentally corrupt 3ds Max software’s settings and be propagated to other MAX files (*.max) on a Windows® system if scene files containing the broken script are loaded into 3ds Max. (The original script seems to have been included with some free 3ds Max scenes that users may have downloaded from various non-Autodesk affiliated online sources.)  Although the MAXScript appears to have been written as a form of copy protection for a commercial plug-in, if affected 3ds Max scene files are distributed and re-opened, they may propagate the corruption problem to other copies of 3ds Max.  (See link for more details.)

 

--

 

CRP MaxScript article:

A 3rd-party MAXScript (hereafter called "CRP"), included with some free, online 3ds Max scene files (non-Autodesk affiliated) may corrupt 3ds Max software's settings and can be propagated to other MAX files (*.max) on a PC. This can happen if the scene files are loaded into a corrupted version of 3ds Max, then re-saved. (See link for more details.)  

 

--

 

If you are having any trouble with the steps in those articles, please create a new support case by doing the following:

 

  1. Log into your Autodesk Account
  2. Go to the upper right-hand corner and click Support > Contact Us > Technical Support, and pick Email.
  3. From there, create and submit a new support case for this, with the subject line "ALC MAXScript issue." or "CRP MAXScript issue."  

Your case will be escalated to Technical Support and Autodesk will use best commercial efforts to work with you directly, to help you fix your 3ds Max installation, and restore your affected 3ds Max scene files (if possible). We strongly recommend that you do not open additional scene files on the affected Windows system until the repairs are complete (if possible). 

 

Thank you and best regards,

74 REPLIES 74
Message 61 of 75
Anonymous
in reply to: attilaszabo

Ok, so tried the suggestions and now have another issue as it now says the app cannot run on my pc. Suggestions?

 

 

max2019_scriptCheck_error.JPG

 

 

 

Message 62 of 75
Anonymous
in reply to: attilaszabo

Security tool is not working, also its not showing in customize menu.

 

Message 63 of 75
hagen.deloss
in reply to: Anonymous

Hi @Anonymous 

 

Thanks for bringing your question to the forums, it looks like you are visiting as a new member to the 3DS Max forum. I want to extend a warm welcome to the Autodesk Community!

 

What version of 3ds Max are you running the security tools for? Just a heads up, 3ds Max 2020 has built in Security tools that will protect against the ALC/CRP corruption.

 

What exactly isn't working? Are you experiencing any strange symbols in the scene explorer, or are lights missing from your scene?

 

Hoping I can help!

 

 



Hagen Deloss
Community Manager | Media & Entertainment
Installation & Licensing forums | Contact product support | Autodesk AREA


 

Message 64 of 75
ichong86DCR
in reply to: lukuanenko

Hi, currently i'm using this Prune Scene to clean my max files. I just want to know is it safe to use this script? I hope it won't disturb my 3ds max software or any max files. Thanks.

Message 65 of 75

Any encrypted file can harm your machine, system and files. You always use it at your own risk.

 

As for this particular script, it is vapid, but harmless.

Message 66 of 75

@denisT.MaxDoctor is right.

Any reason why you would not use the Software Security Tools for 3ds Max? It is supported from 3ds Max 2015 all the way to 3ds Max 2019. See the Autodesk App Store. 3ds Max 2020 has it built in.

 

Best regards,

Attila Szabo

Technical Product Owner

3ds Max

Autodesk

Attila Szabo
Product Owner, 3ds Max
Autodesk
Message 67 of 75
lukuanenko
in reply to: ichong86DCR

Hey, I guarantee a fair job of a script. I am author of Prune Scene and script do only what declared in script manual.

Encrypted only because used license. 

You can safely use it in your work.

Message 68 of 75


@lukuanenko wrote:

Hey, I guarantee a fair job of a script. I am author of Prune Scene and script do only what declared in script manual.

Encrypted only because used license. 

You can safely use it in your work.


Your tool does some job. Sometimes it might helpful. But there are many things that are not optimized and do wrong things, or at least not necessary. Sometimes people need just a specific clean up for their scenes (not 'universal'). Not encrypted script can be easily modified to do what you exactly need.  

In addition, there is no need to trust a promise that it is safe. If all the scripts were open, we would not have problems as in the case of ALC/CRP

Message 69 of 75


@attilaszabo wrote:

Any reason why you would not use the Software Security Tools for 3ds Max? It is supported from 3ds Max 2015 all the way to 3ds Max 2019. See the Autodesk App Store. 3ds Max 2020 has it built in.

 


ALC /CRP 'infection' is a special and isolated case. One moron wrote this rubbish, and infected a bunch of machines around the world. Instead of thinking about how this happened, Autodesk provides a set of highly dubious scripts to 'solve' this particular case. The Software Security Tools has absolutely nothing to do with Security. If you look into the tool's code, you will see that the names of suspicious objects, callbacks, and files are simply hard-coded. Is this a solution, in your opinion? I already got two dozen other names and patterns that are not on your list.
In addition, I have already pointed out to you that there is a mechanism of infection through Modifiers. This problem is still not resolved by you.

 

Message 70 of 75

I have many observations about the effectiveness of your Security Tools. More... I sent you an example file that cannot be "cured" by your tools, but this case was left without comments.

 

Do you still have a question, why do some people ignore the 'Security' Tools?

Message 71 of 75


@denisT.MaxDoctor wrote:
the names of suspicious objects, callbacks, and files are simply hard-coded. Is this a solution, in your opinion? I already got two dozen other names and patterns that are not on your list.

for example, look at this code from ALC_SecurityTool.ms which is coming with The Security Tools: 

 

	-- things to look for....
	m_ALC_script_files = #(@"$userStartupScripts\vrdematcleanbeta.ms", @"$userStartupScripts\vrdematcleanbeta.mse", @"$userStartupScripts\vrdematcleanbeta.msex"),
	m_ALC_globals = #(#physXCrtRbkInfoCleanBeta, #checkLicSerSubCleanBeta, #checkLicSerMainCleanBeta, #CleanBetabaseCC64enc, #CleanBetabaseCC64dec, #runMainCleanBeta, #PointNodeCleanBeta, 
			#px_HiddenNodeCleanBeta, #getNetUpdateCleanBeta, #AutodeskLicSerStuckCleanBeta, #px_SimulatorForModifyCleanBeta, #px_SimulatorForStateCleanBeta, #px_SimulatorSaveCleanBeta),
	m_ALC_callback_ids = #(#RenderLicCleanBeta,#PhysXCleanBetaRBKSysInfo,#AutodeskLicCleanBeta),
	m_ALC_node_names = #("×þ×ü", "¡¡×ý×û"),
	m_scale_script_expression_string = "px_SimulatorCbaCleanBeta"

do you seriously think these are all possible patterns? did you try to match it for Chinese 3DS MAX localization?

 

There is another bad issue with the Security Tools... 

You cut only the "tops", and remain the "roots" in the file. Finding them after your work is much more difficult.

 

 

Message 72 of 75


@denisT.MaxDoctor wrote:

You cut only the "tops", and remain the "roots" in the file. Finding them after your work is much more difficult.


I can say the same about the Prune Scene script (at least as solution for ALC /CRP).

It's just hiding sores, not a cure for the disease.

Message 73 of 75
Anonymous
in reply to: Alfred.DeFlaminis

Hi,

 

I am a 3d Designer who is using 3ds max as modeling and vray as my rendering. I have a lot of issues in counter,may i ask where can I  get a proper help to solve some of my difficulties using both software? Thank you.

 

PS. I am also new to this group,i just came here to find some forums on my problems with regards to my rendering results. Sorry.

Message 74 of 75

Hi everyone,

 

The 3ds Max core team has been working hard to protect against the ALC Maxscript issue.

 

To that end, they have made a few adjustments to the 3ds Max Security Tools recently to guard against ALC2. If you are continuing to experience any issues with nodes in the scene explorer, a Script Controller window appearing on program launch, or other random or unexplained behavior, please download the newest version of the 3ds Max Security tools here, and refer to the updated documentation regarding these issues here.

 

If you continue to experience these issues, please open a support case by following this link.

 

 



Hagen Deloss
Community Manager | Media & Entertainment
Installation & Licensing forums | Contact product support | Autodesk AREA


 

Message 75 of 75
jon.bell
in reply to: denisT.MaxDoctor

Hi Denis,

 

I'm revisiting this thread to follow up with you on your note that you provided files which you say our Security Tools do not fix.

 

Can you please send me a private link where I could obtain these for review by our developers? (Or I can provide you with a private OneDrive folder link if you'd prefer.) Thanks!



Jon A. Bell
Senior Technical Support Specialist, 3ds Max

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Technology Administrators


Autodesk Design & Make Report