Interesting...I'll fire up Visual Studio and see what's going on :up:

Has anyone noticed that Room_QR1 renders incorrectly when compared to Goblin? I just noticed this and I see why. In the GR2 file the model has a Flags, Position, and Rotation data. I assumed, once again, that SH5 was using this model data. Wrong again. SH5 is totally ignoring this model data.

In a nutshell the only thing SH5 is using Flags, position, and rotation wise is the bone's data. Meshes that are 'bound' to bones aren't - the only thing they are bound to in the bones is it's extendeddata.

What a freakin mess....:nope:

SH5 is a real bullsh**, I wonder sometimes why people like you "waste" his time in this piece of crap software (that´s also for me) :wah:

Did you find the problem here? :hmmm:

Sure did. I have to have you select a skeleton from the bone's treeview box first before you can add a new bone. This way all the bones from the skeleton are listed as possible parent bones

The incorrect rendering has been fixed. Turns out that SH5 is using the model's data for only the bones. Meshes are rendered as is:
http://www.subsim.com/radioroom/pict...pictureid=5358

Notice that there are some new checkboxes under the misc tab:
- show world axis
- show camera axis

both of the two above control the visibility of the two little boxes that show the reference axis's for the camera and world

The lock diamond's show controls whether the lock diamond is rendered or not

Makes you wonder how they ever made it to a functioning game in the first place! :har:

Great work chaps, you guys are the future of SH5! :yeah:

They didn't understand the Granny system that's for sure. Just as Privateer said they use about 5-10% of it's potential.


Test version 1.1.67.0 available here: http://www.mediafire.com/?1z2r0186qnuzfq7

Fixes problem of not being able to select correct parent bone when adding new bone and incorrect rendering of some GR2 files
Now to add a new bone you first have to select the skeleton from the bone's treeview box
Adds some new checkboxes under the misc tab

:salute: Hi

Great :yeah:

How do you do, for a view so close to this side of the room QR1 :06:
Personally, I can not bring too near this side of the room :hmmm:

Use the numpad keys 2,4,6, and 8 to move the camera. Then use the mouse to pan/zoom. The numpad keys 2,4,6, and 8 adjust where the eye is looking at and moves the camera. Right mouse button and moving mouse fwd/back is camera zoom not move camera fwd/backward (that's 2 and 8).

By using combinations of the numpad keys 2,4,6, and 8 and mouse movements you have total freedom of movement of the camera. You can see anything and move it anywhere. i.e.: pan camera straight up and then press 8. You will move the camera and it's focal point up.

I have just try the new version : load the QR1 room and clic again on the file menu = error !

You must have got to 1.1.66.0 before I could yank it. I found a last minute error and thus replaced it with 1.1.67.0

Zoom camera all the way in first (right mouse button and mouse forward) before using the 2,4,6, and 8 numpad keys

Room_TRF is pretty baren without everything else. Must be in dry-dock for a refit:
http://www.subsim.com/radioroom/pict...pictureid=5359

Just showing that you do have total freedom of movement of camera

Just about done with the ability to view multiple GR2 files at a time. Actually I have that part coded and working. What I have to do now is if the next GR2 file you load's model is already present (loaded) then I have to give it the already loaded model's position,rotation, and scale data so that it renders in the correct place.

v1.1.67.0 gave you the ability to load multiple GR2 files though the last part above isn't coded in yet.

Ok with the version 1.1.67.0 ,just a little thing a have try to open a hex modified GR2 for remake the CRC checksum ,but we can't no more save just after ,obliged to change a value of bones (and return the original value) or import a meshe to save the file with the good CRC

and thank you for the explanation for movement in editor :up:

Yes I changed that. Here's what I'll do: I'll add a new menu item that is check filesize/CRC value....give me a few...

EDIT: didn't add the menu item. I just forgot to flag the change in the InfoHeader class

v1.1.68.0 available here: http://www.mediafire.com/?iazme3x71k365zn

Fixed bug of when a modified GR2 file was opened whose CRC value and/or filesize was incorrect and you selected yes to correct problem File-->Save was not enabled at start :DL

Now when you correct the problem of the filesize and/or CRC value as soon as file is loaded click File-->Save to save changes to file.