HOME | DD

Riveda1972 — [MMD] How to fix invalid or corrupted models (4)

#fix #hacks #locking #mmd #model #pmx #repair #tricks #tutorial #unlocking #pmxeditor
Published: 2018-09-21 14:23:02 +0000 UTC; Views: 26445; Favourites: 121; Downloads: 41
Redirect to original
Description

Disclaimer: Personal opinions here!
This post contains personal opinions of mine, which would probably not match yours, nor the ones of any other Homo Sapiens living on this planet, solar system, galaxy and universe (I don't know about macroverses and alternate realities, sorry). I usually answer any question and criticism, since they're politely and educately expressed. If you cannot express your criticisms without barking, flaming and insulting other people, you're courtesly invited to not read this post and to not leave comments that I'll be forced to ignore and mark as spam oe to report them to DA moderators.
Legal (and hopefully stupid-proof) disclaimer for both "lockers" and "unlockers"
This (and the previous ones) article is not intended to help or encourage you in violating rules or third party intellectual properties. Authors and editors DO have all the right to protect their works, their intellectual properties, their efforts in sharing reusable contents, and to prevent third party users to not use their work in improper ways (examples: using models in NSFW or too violent contents, using them for alternative purposes like VRchat avatars or in-game mods, and so on).
BUT:
- You don't have the right to intentionally corrupt a file to cause lag and malfunctions on other people's computers and programs
- You don't have the right to decide if a user should use or not MMM, Blender, 3D Studio Max or any other rendering application instead of MMD to render their pics and videos
- You don't have the right to consider as your own property the (3rd party) parts you've freely used to make your edits or to deny further edits

You lockers, please, also remember the meaning of the this warning shown by PMX Editor: 

   

This is saying: An ERROR has occurred while loading the model. Ignore and continue?

Please, take note of the word "Error".
This is not a message informing that you're opening an "edit-locked" model: this is a MALFUNCION warning
I.e. what you consider a "licit locking" is an illicit try to corrupt/invalidate a file and to cause malfunctions on other people's computers.

Previous chapters
[MMD] How to FIX pmx files corrupted by PMX Locker
[MMD] Locking files? No: Corrupting them (pt. 2)
[MMD] PMX unlocking, ZIP/RAR passwords... part #3


How to FIX locked/invalidated/corrupted PMX models: minor tricks
Hello, little hobbits

I'm going to publish a short "addon", or "update" if you prefer the term, to my previous journal entries concerning the PMX "edit-locked" models issues. This is meant as a brief collection of minor tricks. If you've never read the previous chapters and you are searching for a solution to your frustrations when trying to open an edit a "locked" PMX model, it's recommended you read the previous entries, first. The main "unlocking" (or better: REPAIRING) techiniques are exposed better there. The tricks listed below are really minor hacks (sorry, this term could be defaming and insulting for people who are real hackers and not just dummy lamers), but a lot of people commented my previous tutorials complaining for "locking" systems not solved by my main articles. So, here's the rest.

In order of relevance (easier to "hard"):
1) Foreign character sets causing textures to not be displayed (this is not a "lock" nor an "hack", it's an issue with your computer settings!!)
2) Files/Folders permissions ("read only" and "hidden files/folders" hack)
3) PMX file format version hack
4) The "fake blank space hack" (this is, by far, my favourite. Fun. really.)


1. Charset issues: this is not a locked model!!
This is not a trick to "lock" a model, this is just an issue caused by the use of characters your PC cannot display properly. yes the effect is the same: you load the model and you see it as blank, with no textures applied. Consider this is not a try to prevent you editing the model. Some editors/authors just haven't given english names to texture files and/or folders, and when you unzipped the file you have downloaded, your sistem doesn't recognize the "foreign" characters. Sorry for the word "foreign" I'm assuming most of readers belong to the "overseas" communities. This just means that your computer is not set to show japanese/chinese/arabic/hebrew/viking_runes/sindarin_tengwa/[other] characters used by the original author or editor to name their model/files/folders.
You have two solutions for this issue:
1) Set your system to show the foreign character sets you're using (most common ones: japanese and chinese)
The way depends on your local windows version. Just search on google for a quick "how to" enable alternative alphabets and character sets.
2) Manually rename files and folders with standard "western" characters
This is longer and takes more time to be done, but is more useful, by far, if you need to edit the model and you're not familiar with the original alphabet used.

EDIT: sometimes this issue is caused by the way original files have been zipped, and when you unzip them the file names and the folder names loose their original japanese/chinese names. Just search around, this is a common issue. Using some alternative archive managers, like BANDIZIP o japanese/chinese versions of 7zip should solve all of your problems.


2. File permissions (read only / hidden) hacks: a dumb and weak try to "lock" models
Really, I was surprised to hear that this kind of "hack" still works. I've not experienced it, personally. But as some users have reported it, I'm talking about it. Assuming you use any version of MS Windows, the solution to this issue is quite simple, as in most of personal systems users do have administrator permissions or anyway they easely can run commands and operate with administrator privileges. It could have been more difficult if you were using more secure operative systems like Linux, but this is not our case.
Any file (or folder) has some basic "permission" set on itself. these permission concern the right to see or not the file, open or not it in "read only" mode, and open it in write (edit/modify/save changes) mode. There should be another kind of permission, i.e. the "execute or not" as a program, but it's not relevant for our purposes.
The normal state for a useable file or document is to set with visible to all, and with read-and-write permissions.
I.e. you can see the file or folder, and you can freely access it, both opening and editing/deleting/moving it.
Hidden files/folders: if you experience this issue, not seeing the textures files or folders, first of all you have to enable on your system the option "show hidden files/folders". depending on your windows version and localization, this can be done opening the explorer (the file explorer to browse in your PC folders, not the web browser!), open the "tools" menu, and the "folder options" window. Search for the file/folder view setting and check or uncheck the option concerning to show or not to show hidden files and folders and system files. Set it so that you can see also eventually hidden files and/or folders. I also suggest you to check the option to apply this setting to all folders of your system. Just be careful in case you browse in the Programs folder or in any of the system folders and don't try to delete system files that have been hid just to prevent eventual deletion. Once set the show hidden files/folder you should now see the files you were interested in. At this point the only thing you've to do, is to select the previourly hidden files, right click and choose "properties": uncheck the option that sets the files as hidden and you're done (at this point you also could restore the folder options to not show hidden and system files).
Read only files/folders: even easier than the hidden ones. Just select them, right click, choose "properties" and uncheck the "read only" flag. Click "ok" and you're done.


3. PMX format version issues (mostly affecting English PMXE translation and older PMXE versions
This is a caotic bunch of hacks, appearently made to play with the file format version, appearently in order to prevent the most diffused (among the "western" MMDC) PMX Editor versions to load a more recent file version. The last of this issues has been reported to me by LesbianLioness and the real nature of this issue has been suggested by harryhack91 : his solution is valid. Just download the most recent version of PMX editor (at the moment I'm writing it's the 0.2.5.4f), open the appearently "locked" model, resave it with another name, and then you'll be able to open it with your preferred version of PMX Editor.
As an alternative way you can also import the appearently "locked" model in Blender, using MMD Tools plugin to importa and export. Then export it again as a new model. The resulting model can be normally opened with your preferred PMX Editor version.


.
.
.
Now, please, a moment of silence.... *beating-on-DRUMS-like-Stannis-at-King's Landing-siege*
youtu.be/i4kNneOct6A


4. And the winner is... THE "FAKE BLANK SPACE" HACK!!!
 
Yes. The previous ones are not real hacks, just tricks to make harder your life, but without really achieving anything, other than annoying you.
But this "hack" is at least original and fun.
Really, man/woman, whoever you are, you've demonstrated creativity and even a kind of perverted sense of humour I totally like!  

You should know, at this point, what's the main feature of the most diffuse way of "locking"/corrupting models to prevent users to load them in PMX Editor, isn't it? That famous "4th character hack" in the file header definition. The valid and standard PMX file format requires that the first four characters in the file header definition are "PMX ", with a BLANK SPACE after the 'PMX' string ('䵐 ' in japanese charset). PMX lockers usually replace that blank space with a special character, 'ꁘ', setting the first 4 caracters to "PMXꁘ" ("䵐ꁘ" in japanese characters). This way although MMD recognizes the model as valid (but often lagging and malfunctioning if compared to a clean and uncorrupted model), PMX Editor and MMM won't recognize it as a valid PMX format and will prevent you to open in the editor, or worst will prevent you to use the model for animation or picture posing purposes, just because you prefer MMM to MMD.
The fix has been explained in my first journal: open the corrupted file with a hexadecimal editor or an advanced text editor and just replace the fourth character (ꁘ or any other character used) with a blank space, save, and you'll get back the repaired model.

Now, our crucial question: What is a "BLANK SPACE"?
Here's the hack. As most of people are not familiar with hex codes, they prefer to use any text editor to open the files and check for the 4th character to be the expected blank space. This is the way many people has been frustrated, as they saw on their screen exactly what they expected to see: a "blank space", but their model still won't open in PMX Editor.
Here's the trick. A blank space is just what we see on our screens. But there are several ways a "blank space" can be represented in hexadecimal mode.
I.e. what you're looking at on your screen, it SEEMS your expected blank space, but it's not. It's another (similar) blank character.
Have you ever seen the diffeence between "-" and "−"? At a first sight they can be confused, but still if you pay attention you see they are different characters.
With a blank, invisible space, it's more difficult to see the difference, but it's the damn same thing. And this is the reason why you don't detect the hack when opening the PMX model with a text editor.
See here if you want to read deeper about this matter: jkorpela.fi/chars/spaces.html 

For our purposes you just have to keep in mind that the only way to be sure that the 4th character is your expected blank space, is to open the PMX file with a hexadecimal editor. No way to avoid this: the first four character must be 'PMX' and a blank space, the one you get pressing on your spacebar. In hex codes, the first "octet" of numbers MUST be "50 4D 58 20" which is the hex translation of "PMX ". No matter what you see in your favourite text editor.
If none of the previous "hacks" (1,2,3) have been applied AND you see a "blank space", BUT your PMX Editor still refuses to properly load your model, you can be pretty sure that the "blank space" you have seen on the screen of your text editor is not the right one. Try it. Open the file in any hexadecimal editor. You'll see that the 4th couple of number won't be the expected "20" (i.e. the right "blank space") but some other number or combination of numbers and letters. So you know what you have to do to fix the file, now: just overwrite the invalid "blank space", by preference directly typing "20" over the wrong couple of numbers/letters.

 

Have fun

ps: I apologize, as usual, for my poor and full-of-orthographic-errors english

Related content
Comments: 59

Riveda1972 In reply to ??? [2018-10-09 06:18:58 +0000 UTC]

you mean..?

👍: 0 ⏩: 1

kupocygirl87 In reply to Riveda1972 [2018-10-12 09:57:00 +0000 UTC]

It's petty shit, that's what I mean.

👍: 0 ⏩: 1

Riveda1972 In reply to kupocygirl87 [2018-10-12 11:37:34 +0000 UTC]

Locking models?

👍: 0 ⏩: 0

harryhack91 In reply to ??? [2018-09-24 08:14:22 +0000 UTC]

While I was reading through I saw it coming after reading "As most of people are not familiar with hex codes, they prefer to use any text editor". At that moment I knew the trick had to do with using a different unicode character. That's why I address people to use and hex editor on my tutorial. I must recognize it's kinda a smart trick to fool people who use a standard text editor instead of an hex editor. Still, it's just a child's play for advanced programmers like me (or actually anyone more familiar with hex codes). However, I'm curious about the real nature of the PMX format version hack, there is no doubt that it's exploiting some bug in older versions of PMX Editor. And at the same time it keeps the format valid so it load even on Blender with MMD Tools. From this list, that's the only one that I would consider a real hack.

👍: 0 ⏩: 1

Riveda1972 In reply to harryhack91 [2018-09-24 09:17:28 +0000 UTC]

"At that moment I knew the trick had to do with using a different unicode character. That's why I address people to use and hex editor on my tutorial."
Yes, me too. Or, at least, a text editor able to open binary files in hexadecimal mode, like UltraEdit pro (commercial) or Notepad++ with the hex edit plugin installed (opensource).

Again, I'm curious too. As we've "found" the solution, but without having identified for sure the hack.
This is the reason why I initially called the fix as a temporary one.

👍: 0 ⏩: 0

HazyGem In reply to ??? [2018-09-21 14:25:50 +0000 UTC]

I just want to use a model and these Mofos still don't learn and corrupt the damn pmx file

👍: 0 ⏩: 1

HopexDespair53 In reply to HazyGem [2018-09-21 14:34:09 +0000 UTC]

Bitch I am right here.

👍: 0 ⏩: 1

HazyGem In reply to HopexDespair53 [2018-09-21 14:38:23 +0000 UTC]

lmao XD

i didn't mean you tho

👍: 0 ⏩: 1

HopexDespair53 In reply to HazyGem [2018-09-21 14:42:18 +0000 UTC]

lol oki cuz i'm one who locks models oof

👍: 0 ⏩: 0


<= Prev |