Mad Compile Time Optimizer - Speed up your development!

Please send me your invoice number to support@madpixelmachine.com if you'd like to test this version. It may be unstable, so if you're not using version control system I strongly discourage trying it

@iamsam Thanks! I will greatly appreciate testing of this version. I don't want to release something that will break anyone's project. It's just too important to have this working all the times.

Everyone be careful though. I cannot guarantee that Unity upgrades won't break anything. Of course we have the access to beta and RC released, but as Unity 5 were released the final version were different than the last RC version for some reason. Backups and/or SCM for the life!

 

Thanks @genail, the dependencies weren't external to the libraries, it was the libraries themselves that were missing.

For example, after omptimization, the InControl namespace was just missing, so all my projects scripts referencing that namespace had errors. I tried rebuilding the VS Project Files, and relaunching unity, but nothing seemed to work.

Good news is, this morning I re-optimized them, and everything just worked.. weird!

In terms of version of Unity, I'm currently on 5.1.2.
Cheers,

 

Have you seen this error only in Visual Studio or in Unity too?
From my experience Visual Studio project may not get refreshed sometimes.

Anyway, good to hear that the problem is solved!

Cheers!
Piotr

 

I just bought the asset when I read this, it's the main thing that prevented me from purchasing in the past, looking forward to the update!

 

I just bought and tested this.
For convienience I just quickly optimized my biggest assets which are
- Playmaker (+ ITween)
- Behavior Designer
- Inventory Pro
- 2D Toolkit

Compile time went down from ~9400 to ~4700. Pretty nice for just a few minutes of trial and error.
However i am left with a weird "Do Upgrade" item in the tools tab. Inventory Pro briefly disappeared from there.
Any idea which asset leaves that item? Or is it the Optimizer itself?

First impression is that this asset is well worth it. Even if it takes a while for 4-5 seconds to add up to anything substantial, imho it's also a matter of user experience. Spending some time once to optimize is much less annoying than spending the same time waiting in 5 second chunks.

 

Hi, a bit confused about things behind MCTO.
1. My new game use a lot of assets(more than 10), but I don't feel significant difference. That makes me wondering what exactly "compile time" means. Is that means each time I hit "Play" or "compiling" after edit some scripts?
2. When will optimized scripts get compiled? Is that base on a "dirty" property?
Thanks.

 

Thank you for purchasing MCTO

Unfortunately I don't know what asset is responsible for this :-( Is this in the main menu? Search in the source files for "Do Upgrade" text.

@zhuchun

1. Compile time means the time needed for your project to recompile after your game scripts has been changed.
2. These are compiled right after the optimization. The whole thing is to not compile these scripts as frequently as your own scripts. MCTO is separating 3rd party scripts so these can be compiled only once from your own scripts that are changed more frequently

Cheers!
Piotr

 

Hi, I just purchased this. Thanks, so far it has shaved off a few seconds. However i am getting an error regarding duplicate keys on every compile. I'm using Unity 5.2:

Code (CSharp):

1. ArgumentException: An element with the same key already exists in the dictionary.
2. System.Collections.Generic.Dictionary`2[System.String,MadCompileTimeOptimizer.Directory].Add (System.String key, MadCompileTimeOptimizer.Directory value) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Collections.Generic/Dictionary.cs:404)
3. MadCompileTimeOptimizer.OptimizeWizard.LoadSelected ()
4. MadCompileTimeOptimizer.OptimizeWizard.OnEnable ()

If I could see which keys are duplicted I might be able to fix it.

Thanks.

p.s I also get the "Do Upgrade" text in my menu.

 

Hi!,
Thank you for purchasing MCTO.

This is... not possible! This would mean that there are two directories with the same GUID... Or the scanner is faulty...
Can I ask to send me your project? Please also write to me to support@madpixelmachine.com with your order no. I will send you the sources.

Cheers!
Piotr

 

Hi,

I bought Mad Compile and were using happily in my current project, until today, when I had to revert the optimizations for the first time, in order to update a plugin (Master Audio). I went to the Revert menu and, agh:



Where should these logs be? What do I do? :O I can assure you that I'm not crazy and I optimized various assets (which are now partly in the Standard Assets folder, plus Mad Compile correctly tells me that there's nothing to optimize anymore for those original assets folders - including the Dark Tonic Master Audio original folder).

 

Hello Izitmee,

What MCTO version do you have? Logs can be found inside Mad Compile Time Optimizer/Resources directory. Can you send me zipped Mad Compile Time Optimizer directory to support@madpixelmachine.com?

Cheers!
Piotr

 

Thank you, mail sent!

 

OK I know what happened. For some reason main DLL file GUID has changed. You've said that you've removed your Library directory once. Did you have "Visible Meta Files" option enabled at the time being? If not, all the GUIDs in your project were regenerated and all references lost. Check your scenes, materials etc.

Of course there's other possibility like you accidentally remove meta files (what you shouldn't do under any circumstances).

You can recover MCTO from this situation. Follow these steps:

1. Move Mad Compile TIme Optimizer/Editor/Resources somewhere outside MCTO directory:



2. Remove Mad Compile Time Optimizer directory and import it again from the asset store.

3. Move back only the *log files.



4. Remove old Resources directory (the one outside MCTO directory)

Revert should now be working



Please let me know what about references in your scene, materials and prefabs, are these gone too? This is not MCTO fault of course, but I'd like to understand what happened here.

Cheers!
Piotr

 

Hi!

Thanks for the instructions, gonna try it now. Before that, some more info...

If it's a GUID issue, I agree it must not be an MCTO issue, but it's still very strange. I use "Hidden Meta Files", but just because I have set my system to show hidden files, and that way they're actually more visible. The meta files are correctly versioned and I lost no other reference. I use this workflow since always, never versioned the Library, and never lost a reference when regenerating the Library (not only on personal projects but also on team projects), so I'm kind of puzzled here.
I'm also sure I didn't remove any meta accidentally.

Anyway, going to try your fix now, crossing my fingers Will let you know in a short while.

Cheers!
Daniele

 

It worked! Though, I have an error now (but MCTO seems to be working correctly anyway) that is spawned each time I open or recompile the project or get into play mode:

Code (csharp):

1.  
2. ArgumentException: The Path does not have a valid format
3. System.IO.Directory.GetFileSystemEntries (System.String path, System.String searchPattern, FileAttributes mask, FileAttributes attrs) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.IO/Directory.cs:487)
4. System.IO.Directory.GetFiles (System.String path, System.String searchPattern) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.IO/Directory.cs:308)
5. System.IO.Directory.GetFiles (System.String path) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.IO/Directory.cs:303)
6. MadCompileTimeOptimizer.Upgrade.DoUpgrade ()
7. UnityEditor.EditorApplication.Internal_CallDelayFunctions () (at C:/buildslave/unity/build/artifacts/generated/common/editor/EditorApplicationBindings.gen.cs:280)

 

@Izitmee
Do you use any Version Control System? Please verify when and why meta files has been changed.

The error above is because is expects the Resources directory to have GUID equal to dd9b419ee69821549bc79933423c6d37. Please edit the Resources.meta file and change the guid in there to dd9b419ee69821549bc79933423c6d37 and the error should be gone

 

Ah, I see. Fixed, now working perfectly

I use GIT, and the Resources GUID was correctly changed when I deleted the MCTO folder as you told me and reimported it again (since the original Resources GUID was already taken by the folder you told me to move outside of MCTO ). All great now thanks, time to write a nice review.

 

Strange why this happened though...
Well... The important thing is that this is working now!

Thank you!

 

Hey ,
Is it possible to add (screenshot from the optimize window):

to the revert window too?
I want to have a cleaned up folder structure, and I don't want to revert all assets inside a single folder each time, like this:

Thanks in advance, John

 

Hi!
I believe this can be done by selecting each asset separately

Instead of selecting your Asset entry for optimization, please select all its children individually.

If this is now what you're looking for, please let me know

Cheers!
Piotr

 

Hey,
Thanks for your fast reponse!

That's it.
Sorry, should have tried that before.
Reduced my compile time from 12 seconds to 2.5 seconds (I'm using 14 assets currently), that's an cool improvement of 480%, great!

Best wishes,
John

 

Wow! I think this is the record
Please let me know if you will need anything!

Have a nice day!
Piotr

 

@genail I had a look at your video for Mad Compile Time Optimizer and had one question for you. After we optimize the other plugins into the Plugins or Standard Assets folders, can we delete the original folders they were copied from?

For example we optimize the iTween folder from the root folder to the Plugins folders, can we then delete the iTween folder in the root?

 

Hello @Ben BearFish
It depends.

MCTO is leaving the original directory structure where it was, because some scripts may:

• Depend on it
• Have some other assets in there

MCTO can rectore this direcotry structure when you will revert your assets, but deleted files that are not scripts won't be restored. It's always safer to keep the original directory where it is

Cheers!
Piotr

 

When trying with MarkUX(it's in asset store), MCTO failed.
It failed while optimizing and can't revert well.
Could you check this, genail?

 

Hi! Please write to me to support@madpixelmachine.com .

 

Hi @genail ! I'm currently in the process of making things easier for my team : http://forum.unity3d.com/threads/streamlined-3rd-party-extensions-dll-creation-with-utomate.369892/

I just realized that you are the one I was inspired by in the topic I quote in my message, thanks !

Do you plan to add this feature (dll compilation) to your plugin ? Or do you think it would not be worth it ?

 

Hi! @RDeluxe
I'm glad that I or something I am doing could be an inspiration to anyone

Unfortunately I'm not planing to add DLL compilation feature to MCTO, but if you're interested, I wrote some ruby scripts that are helping me compiling my code into dlls with only one command. If you will need any help with these, please PM me or write to support@madpixelmachine.com

Cheers!
Piotr

 

Hi !

Well, I played around with uTomate and managed to compile everything (witout keeping guid links, which broke all my components, but I was first testing performances). Compared to just moving scripts in the Standard Assets folder, the performance gain is minimal as far as I can see. I updated my topic to reflect this, I guess I'll try to automatize the process (or buy your asset, if I don't have time to play around )

Thanks for your answer, I already found your scripts. I don't understand Ruby at all (what a weird syntax !) but the process helped me a lot.

 

Good luck!
Inside my scripts you can find code that is responsible for re-linking the GUIDs. If you compile a script it receives a new GUID based on dll file id and a script name. If you will have any questions about that, please write to me anytime

 

Hello, genail.
After upgrade 5.2.3p3 from 5.2.2p2, mad compile time optimizer doesn't work anymore.
Does unity change the way of compiling?

 

Hi!

What exactly is happening?

 

Compiling time is same between pre-optimization and post-optimization.

 

I don't see why this may be happening :-(



7660 - warm-up
4XXX - before optimization
5751 - warm-ip after optimization
2XXX - after optimization

Could you please send me screenshot of your Optimize window? I'd like to see what assets you have out there and what is optimized.

Cheers!
Piotr

 

Please could you try with patch release?

http://beta.unity3d.com/download/383123ade41b/Windows64EditorInstaller/UnitySetup64-5.2.3p3.exe
http://beta.unity3d.com/download/383l123ade41b/Windows32EditorInstaller/UnitySetup32-5.2.3p3.exe
http://beta.unity3d.com/download/383123ade41b/MacEditorInstaller/Unity-5.2.3p3.pkg

my compiling time was 7~8s but it became 30 seconds with 5.2.3p3
(and 30 seconds was full compile time)

 

Yep, it's broken. But that's not my fault. For some reason Unity 5.2.3p3 is forcefully recompiling all assemblies, even those with unchanged files. I believe it is a Unity bug, because for 5.3.0 it is working just fine.

Unity lately has changed how and when files are recompiled. Is file has been changed, but contents remain the same, Unity won't recompile the assembly. This is a good change, but it looks like someone did the merging incorrectly

Please report it, and/or downgrade or upgrade your Unity installation to 5.3.0.

Piotr

 

I am very happy by hearing 5.3.0 is ok.
Although I can't use 5.3.0 now, I got peace of mind.
Thank you very much.

 

I'm having some trouble using this with Apex Path. Some AP components utilize "Entity Attributes", which can be defined by creating a specially flagged enum yourself or with a utility which will automatically create one for you. For some reason, optimizing Apex Path prevents its components from finding this enum. The enum, or at least the one created by the utility anyway, exists in a file that is located in the root folder of the project.

 

Hello Lork,
That's because when you're optimizing an asset, it is moved to different assembly. Main assembly sees all the code but editor scripts. After optimization it is moved to Plugins assembly that sees only another Plugins code. In theory to make it work you will have to move generated enums to Plugins/Standard Assets directory (depending where you're optimizing Apex Path).

If this won't help, please leave Apex Path unoptimized. This also applies to other assets which are doing similar things with scripts.

Cheers!
Piotr

 

That makes sense. Moving the file to the right directory fixed things up, thanks!

 

I've been trying to reduce 20 second compile times with a big project that uses Playmaker- Could this asset reduce this time? If so- I can still upgrade Playmaker and use it normally once it is optimized? Thx!

 

Hi @mdotstrange ,
It can be used with Playmaker, but remember that you have to optimize all classes that Playmaker may use. Playmaker scans for actions and if some of them won't be optimized, it won't be able to find these.

Don't worry if it won't work. Please get back to me then. If I won't be able to help (there are some cases like that) and/or you won't be happy about the results I will refund your purchase

Cheers!
Piotr

 

Thanks Piotr- just bought it-

I ran the optimization and I'm getting these errors from some Playmaker actions that I wasn't in the original project-

So this is because something wasn't included in the optimization?

 

Most probably yes, but this is first time I see an error like this. Is ArrayListStringJson.cs your own script? What it does?

Edit: Please write to me to support@madpixelmachine.com.

 

I also get "Do Upgrade" in my Main Menu->Tools menu.


I searched my assets directory and found the source of the message: MadCompileTimeOptimizer.Editor.dll


I'm using 5.3.5.f1 under windows 7 64-bit and I'm still seeing 17 second compile times after optimization. I guess Unity has decided to recompile all DLL's on every change, even those in the Standard Assets folder.

 

Hi!
Unfortunately MCTO does not work correctly with Unity version higher than 5.3.4f1 due to a bug that recompiles all assemblies on source code change. The bug has been reported and I am hoping for the Unity team to resolve it soon. For the time beign I recommend to downgrade to 5.3.4f1.

About "Do Upgrade" item. I have to investigate why it is displaying. I'm not sure what it was for... I will investigate it as soon as I will be back from holidays.

Cheers!
Piotr

 

Can we add our weight to the bug?

Sadly 5.3.4 crashes my project. (Although 5.3.5 also does so, it's in a new way!)

 

There is a note in a patch about this. In 5.3.5p7 :

• (804864) - Editor: Fixed an issue causing unnecessary script compilation, and improved compilation error handling

We are downloading and testing now.

 

Oh dear! Wish I'd known this yesterday -- I was at the UK's biggest gamedev conference and there were Unity people there we could have pinned-down / bribed ;-)

Are you pursuing more information about this via other channels? Again, anything we can do to add voices? (since it can make such a big difference to compile times.)