Forum posts

This problem doesn't looks like the usual problems/limitations some Studiomdls present.
I suspect it's a Crapender issue.
Or bug with "Crapender Source Tools", or some accidentally tweaked unnecessary setting/option somewhere in the plugin or Crapender.
Or "Crapender Source Tools" doesn't like the new Crapender version, etc...
As a general solution you can try different combinations of old versions of "Crapender Source Tools" and Crapender.
Also check for some tweaked settings/options somewhere in the export plugin or in Crapender.
Altho I don't have a clue what settings/options could do this stupid "sanitar bounding box X number of pixels away from the edges"...

First, some copied info from the .nfo file from the above link .iso :

This package is an "hybrid install", witch means that I used a modified install procedure from ET's CD-ROM Ver.1.0, put the 1.2 engines from WarezArt in it and completed it with Maps & Textures from ET's CD-ROM Ver.1.1.

That's why my version shows 1.1 in the screenshot, but who knows what version is this "hybrid" : 1.0, 1.1, 1.2...

There are many cracks and updates in the .iso with no clear instructions what to do (complete mess), so after some tries and errors, I find myself this to be working :
1. Install from CD:\SETUP.EXE.
2. During the install procedure, select the "Custom" type of setup.
3. Uncheck the "Tutorials" and the "Rainbow Sentinel Lock Driver".
4. Copy CD:\UPDATE\MAXCRK1\3DSMAX.EXE to the main install dir and overwrite.
5. Right click 3DSMAX.EXE and set compatibility mode to Windows 98/ME.
6. When you run the program you will still get the error (you can close the error), but the application doesn't terminate.
7. Have fun

Use this :
https://archive.org/details/3dsmax12_201907

Would the Sentinel Drivers still need to be installed first or are those only necessary on Windows 98?

I will post install instructions later, as this install is more tricky.

A general note : You should use these old programs only to convert/export the old model source files to a new suitable format for use/edit with modern 3D editing software and compilers.
I have ... and :
3D Studio Max 1.2 was able to run only in XP for now
3D Studio Max 2.5 was able to run only in 98 for now
3D Studio Max 4 was able to run only in 98 for now
3D Studio Max 9 was able to run only in XP for now
Putting files inside and out of Win 98 virtual machine can be tricky, but it's doable. For easy file transfer in and out of the VM you can use ver.1.2 as you can see from above, as it's mega easy to transfer files to a XP VM ,cos Guest Additions Add-On WILL work. I can help you to install v1.2. Just use shared folder on host as a network share in the guest, it will work all the times compared to drag and drop.

I wonder what Keys do i use?

The one from the .NFO.
Pressing space or enter INSIDE the crack dos program before closing is MANDATORY.
I'm familiar only with working with "modern" models, can't help you with compiling the 0.52 Alpha models.

Even better - here is ver 1.1 (hybrid) running perfectly in Virtualbox 5 on Win XP SP3 x86 :

https://archive.org/details/3dsmax2.5 works fine for me in Win 98 SE virtual machine (Virtualbox 5 and Microsoft Virtual PC 2009).
In Win 98 first install SENTINEL/WIN_95/SENTW95.EXE, then install the 3D S Max with keys, and then apply CRACK/3DSCRACK.COM to the main installed dir and run it, inside it press space.
Other possible reason for not working is maybe what you used: Windows NT 4.0...
Getting a D3D or OpenGL accel. in Virtualbox 5 or Microsoft Virtual PC 2009 for Win 98 however is a long talk... Very long...

Can admin rename this thread to a more suitable name, so someone with the same problem can find this thread and script more easily?

And it should run on almost any OS.

I have Python 3.5 and 3.7 custom build for Windows XP that works (3.4.4 is the last official version that supports XP).

So, here's a Python 3 script...

Python versions 3.5 and below gave me a syntax error with the script, but versions 3.6 and up worked for me.
I assume they changed a syntaxis between these versions, so there is a minimal Python version requirement for your script, it's not like any 3 version will work.
So... it worked for me, everything is done ... Not!
Although the model looks OK in the model viewer, I think, there is a slight bug/miscalculation in your code, which misplace one of the UV coordinates :Interesting to see about that.
Anyway, thanks!
YOU ARE GOLD!
Barney: Now ... about that beer I owed ya!
Check your PMs!

That probably means I guessed the wrong texture size.

Nope.

Or there's something else going on.

I strongly and sadly suspect this.

Perhaps you could share this model so I can do some proper testing?

Here is the model and the latest Paranoia 2 MV, so you can see for yourself what the opposite conversion do to the texture coordinates:
https://www.mediafire.com/file/m55rw1nnxtdbkin/attachment.zip/file
Thank you for your time (like... for 1000000th time helping me)!

Thank you for your answer!
However, there are two problems:
1) I need a PRACTICAL way to automatically convert ONLY all UV coordinates inside the .smd file, which have its own syntax and other data/digits as well.
I'm NOT even a beginner programmer!
I used M$ Excel to open the .smd and apply primitive functions to only the coordinates data.
To practically use the code you proposed, I need it converted as M$ Excel worksheet formula.
Or converted as Free Pascal code, so I can write my own program that read the .smd file and convert only the UV coordinates.
I can't "program" on anything else, anything new or anything the masses use nowadays
(The Python mark the ? symbol in isPositive ? 1 as an error and don't even compile, BTW.)
2)

Xash3D uses a new "half-float" UV texture coordinates inside the smd/mdl, while goldsource uses the old "fixed-point" UV texture coordinates.

Disclaimer: This is the only info I found, it's not my statement!
I'm not sure if it's true, or if there is more functions involved than just simple conversion from "half-float" to "fixed-point" (which I strongly suspect).
For example, how to interpret 32.03125 ? It's not in the 0.0-1.0 range.
In the latest Paranoia 2 MV, in the EDITOR tab, there is a button, that is supose to convert an old .mdl file with fixed-point UV texture coordinates to the new half-float .mdl (the opposite of what I want).
I observed what happened to the coordinates in the TEXTURE tab after such conversion, but couldn't figure-it-out/reverse-engineer-it.
Some enlargement/multiplying and 90-degree-rotation/U<->V-exchange and crazy shit like that may be involved
Due to 1) I can't test what you proposed for now.
I was hoped, that someone, who knows the exact process of conversion would post the true solution, someone who codes model viewers, like Solokiller for example.
Not a solutions based on my ASSUMPTION!
So, I'm stuck for now

Hi.
So, Xash3D uses a new "half-float" UV texture coordinates inside the smd/mdl, while goldsource uses the old "fixed-point" UV texture coordinates.None of the 6 DIFFERENT mdl decompilers I tried produce proper GOLDSOURCE UV coordinates inside the decompiled smd, that should be in the 0.0 - 1.0 range.
What I see inside the smd:

triangles
pop2.bmp
6 -1.233950 7.157183 18.669037 -0.145192 0.989398 -0.003142 28.638672 40.001953
5 1.172300 7.157199 18.669054 0.145192 0.989398 -0.003154 28.638672 40.416016
8 1.175211 7.219243 16.660397 0.143158 0.989051 0.035837 28.541016 40.416016

I am too lazy to UV remap the model from the ground up all by myself, so I decided to try to mathematically convert the numbers.
I tried some simple math functions/arithmetics on this coordinates, but with no luck (it's look like it's not something VERY simple).
So, my question is:
Did someone knows what complicated math function to apply to the coordinates to convert them from "half-float" to "fixed-point".
Please no noob answers, propose something only if you know exactly what I am talking about and how to solve the problem.
Thanks in advance!

[... you want to place the camera on a specific axis facing the model ...]
Initialy, my idea was adding an options/choises for placing the camera on the +X -X +Y -Y +Z -Z axises, and the camera to point perfectly perpendicular at the zeroes/crossing of the other two axises, that make a perpendicular plane to the camera axis. The distance betwen the camera and the other two axises can be automated, so the whole model is viewable, no model parts going out of the 3D view planel, or even better, it can be added an option to select that distance by number, or the user sliding along the axis (which means practicaly: zoom in and out), so a user can keep it constant when rotating around the model, which is more convinient if you ask me.

But then I realized, that it will be way way better if there is an option for switching between the proposed above and this:
Imagine the model have a perfect geometry center (center of mass). Imagine all 3 axises cross at this center instead of 0. Now if place the camera on any of this new "center of mass axises", the user will see the model better, because the "axises that cross at 0" are usually way way under the model compared to "center of mass axises". Everything else stays the same as above.

[... and then be able to switch between any camera mode (aside from first person view) while still having the original camera origin and angles ...]
No. I only suggest, that after placing the camera on an axis as described above, the user can move/rotate/zoom/roam it freely like usually/before from that axes position (go away from that axis). I just mean, that the view/camera shouldn't stay locked on the axis until explicitly other predetermined camera position is selected.

This is just a basic predetermined top, front, right side, etc. scene view in most programs. Goldsource model viewers just only have: start from only one option - center view (front view) and then you "free roam" around the model.

Aside from that, is Windows XP 32 SP3 build for HLAM even possible?

Sorry for suggesting a thousand things

May I suggest two features:

• Adding an option for switching between an orthographic projection and a perspective projection for the 3D view.
• A predetermined perfect top, front, right side, etc. model projection views, that can freely morph into a free rotating/zooming/roaming afterwards.

I was in a big need for such features, while I was modeling for goldsource and none of the goldsource model viewers had them.
Other programs that can read .mdl files had them, but they lacked other much needed basic goldsource model viewer features at the same time.
Excuse me, if this is not the right place to post requests.
Thanks in advance!