Unable to enter your WordPress password when trying to log-in? Here is an easy solution.

I recently encountered a problem in which it was impossible to login to the WordPress backend/admin area since the password field was not accepting any input. The same problem occurred on all the browsers I tested it in. It seems like an update might have broken something in a theme or a plugin. Finally there was an easy solution to the problem:

Just open the developer tools of your browser, target the password input field and delete the bit where it says “disabled” from the source code (displayed typically on the right side of you browser window in the Developer tools panel). Now the form field takes input again and you are able to login and update your plugins/theme if needed.

Multiple scene views in Unity 3D

Sometimes it’s useful to see the 3d world you are creating from multiple different angles simultaneously. Many 3D programs like 3Ds Max even offer quad views that have four different angles available. In Unity you can view your scene from multiple angles in the editor by right-clicking on the scene window tab at the top and choosing “add tab” and then “scene”. You can now drag and drop this new scene window tab to a place in the interface that you prefer and change it’s view angle to your liking. One way of working could for example be to have always one top view available and next to that one free view.

Examples of Brackets plus the Emmet extension

Here’s how the Emmet extension for Brackets can really speed up your workflow:

-type #mydiv and hit tab to get <div id=”mydiv”></div>
-type lorem and hit tab to get lorem ipsum text
-type #container>.col-sm-4*3 and hit tab to get
<div id=”container”>
<div class=”col-sm-4″></div>
<div class=”col-sm-4″></div>
<div class=”col-sm-4″></div>

Strategies for multi-scene workflows

I have been trying to find a workflow for animating in Blender that makes it possible to keep tweaking the model after the animation process has already started. An ideal solution would allow the user to link the same object into multiple scenes and animate them separately in each one of those scenes, without messing up any other scenes. Editing the mesh in one scene should automatically ripple into all scenes. This, however, is unfortunately not easily achieved in Blender. Here are some approaches that I have tried and their pros and cons:

Option 1: Separate file for the model and the use of proxies

This first option goes basically like this:

-Create your model and armature in a separate .blend file, say a file called “Character”
-Select all parts of your model and the armature and group them together (ctrl+G)
-Create a new .blend file called something like “Animation”
-Use the file –> link option to link the group from the “Character” file to this “Animation” file
-In order to actually select or animate the armature, go to object –> make proxy and choose the armature from the list
-Now you can animate the armature

+ Changes to the “Character” .blend file will automatically reflect to all other .blend files linking to it

– Sometimes laggy
– Changing things like shape keys need complicated driver setups (shape keys need to be driven by the armature)
– You can’t make any changes to the mesh without making it also a proxy and making the mesh object a proxy will lose all the modifiers it might have had

Option 2: Sharing armature and mesh data between scenes

This option works in the following way:

-Create your object and rig in Scene 1
-Animate your rig in Scene 1
-Create a new Scene (Scene 2) using the “link objects” option
-In Scene 2, create a new armature (call it Scene 2 Armature) and then link the original armature to it in the “object data” settings (the very first option there “armature data” allows you to link to other armatures). You have now the same exact armature, but without the animation
-In Scene 2, create a new mesh object and in the “object data” tab link the original mesh from Scene 1 to it
-Select the new object, then shift select the original object and transfer the vertex groups by clicking on the little black triangle in the vertex group settings and choose “copy vertex groups to linked”.
-Add the armature modifier to the new mesh object and point it to the Scene 2 Armature -object
-You have now the exact same setup from scene 1, but without the animations

+ Changes to the armature or mesh in Scene 1 will automatically update to all other scenes

– Takes some time to setup every time you create a new scene
– Shape keys won’t work independently: animating a shape key in Scene 1 will create the same shape animation in all scenes. In my opinion this renders the workflow useless.

Option 3: Make full copies out of the scenes but manually link the mesh data when you update the mesh

This option works like this:

-Create your mesh and rig in Scene 1. Name your mesh object something like “Character Master”
-Animate it in Scene 1
-Create Scene 2 and use the “full copy” option
-This will give you all the same objects and positions and animations from Scene 1 but you can now manually edit them and the changes won’t reflect back to other scenes
-When you update your character design in Scene 1, you do the following procedure in all the other scenes:
*Select the object that needs to be updated
*Go to the “object data” tab and link it to the original mesh (Character Master), this will update the mesh.
*Severe the link immediately by clicking on the little number next to the name filed (in order to make a single user copy). This will make sure that animating things like shape keys in Scene 1 won’t show up in Scene 2.

-You have full control over everything: shape keys, the armature, modifiers etc
-There is no danger of messing up things in other scenes
-Fast to setup

-You need to manually update your meshes in all scenes when you make changes to the master mesh in one scene
-If your mesh in Scene 2 had shape key animations, you lose them in the update. You can remedy it a little bit by copying the shape key keyframes in the dope sheet and pasting them back to the updated object. Note that you need to first hit the i-key once over the shape key slider to get the appropriate animation channels (otherwise you will get an error when trying to paste).

Enabling Microdisplacements/Adaptive subdivision in Blender

Here are the steps for testing out the new microdisplacement possibilities in Blender:

1. Switch to Cycles render engine
2. Go to user preferences –> system –> enable opensubdiv compute (choose CPU as the compute device unless you have a good graphics card)
3. Set feature set to “Experimental” (on top of the render settings)
4. Add a subdivision surface modifier to the default cube and check “use opensubdiv” and “adaptive”
5. Add a material to the cube and set it’s displacement to “true” instead of “bump”
6. Go to the node editor, add a noise texture and connect it to displacement
7. Control the intensity of the displacement by adding a math node in between and setting it to multiply
8. Turn on preview rendering (in viewport shading). You might need to tab between edit and object mode sometimes to refresh the preview.