I’m writing this because that’s some Unity stuff I’m always talking about with other developers so I tought it might be nice sharing it online.
Dark mode for free (works great, no weird program)
If you want to enjoy Unity Pro’s dark interface without paying for Unity Pro, there is a simple way. You just need to erase a single letter in the executable.
- First, download the latest portable version of x64dbg on source forge : https://sourceforge.net/projects/x64dbg/files/snapshots/ (download the latest snapshot, don’t click on the green button).
- Open your Unity install folder.
- Copy and paste Unity.exe, elsewhere (like your desktop).
- Execute the 64bit version of x64dbg.
- Click on “Open” in the top left corner of x64dbg and select the original Unity.exe in the install folder.
- Click on “Symbols”.
- Click on “unity. exe” on the left
- In the search bar in the middle of the screen type “getskinidx” (this step might be laggy).
- Select the line that says “GetSkinIDX….” then double click on it.
- Now you can see multiple lines, in some of them you can read “jne”. Depending of your version the “jne” line you’re looking for may vary (it should be the second or the third).
- Double click on a “jne” line and change “jne” for “je”.
- Press Enter.
- Close the pop up window you just typed in.
- Click on “Patch”
- Click on “Patch file”
- Select you copy of Unity.exe that’s on your desktop to be your patched file.
- Patch it.
- Close x64dbg.
- Go in your Unity install folder.
- Rename the original Unity.exe “Unity_old.exe”, don’t touch the name of the copy. This is your untouched original backup in case you break Unity.
- Cut the Unity.exe that’s on your desktop and paste it in your install folder.
- Run Unity (if you use Unity Hub launch Unity through it).
- If Unity is in dark mode you won, if not try another “jne” line, don’t forget that you should only have a single “je” at a time.
Here is a video tutorial (not mine) :
MonoDevelop on Windows without compiling it
Unity has been shipping with Microsoft Visual Studio (10GB of hard drive space, Microsoft developer account required, closed source) for a while now, but before it was shipping with MonoDevelop, an open source IDE.
If you want MonoDevelop on Windows you have to compile it yourself, and that can be painful or you might even decide not to try.
But there is a simple way of getting MonoDevelop for windows without compiling it, you just need to install the latest Unity 2017 LTS which was still shipping with MonoDevelop. Be careful to tick the case to install MonoDevelop. Once the install is over, go to the install folder of Unity 2017 LTS, cut the MonoDevelop folder and paste it with your other softwares. Now you can uninstall Unity 2017 LTS, then launch you current Unity version and under Edit>Preferences>External Tools browse the path through the MonoDevelop folder to make it your default script editor.
Optimizing in-editor performances on a heavy 3D scene.
On a heavy scene like the level from the FPS Sample you can suffer from serious performance issues even on a pretty decent hardware.
To get back some of that power you can tune your Scene window, of course you’ll think of the obvious settings : turning off the lighting, the sound, displaying the scene in wireframe…but one thing I didn’t realize at first is that guizmos are so ressource intensive. Guizmos are really the ones you should turn off first, maybe just keep the ones you need.
ProCore Tools : BSP-like blocking out / Handy tools for level building
So far ProCore has made three tools, available on the Unity Asset Store : ProGrids, ProBuilder, and PolyBrush. They have been acquired by Unity and are now available through the Package Manager in the editor.
I’m not going to explain what these tools are for, it’s pretty well explained on the developers’ website : http://www.procore3d.com/
For me now, ProGrids and ProBuilder are always in my projects, that’s a no-brainer. Previous versions were unstable and crashed a project for me, but nowadays it seems pretty tough.
Augustin Liglet 