.ski files

Hmm i tryed some ski mod with ski blender but i get lost in the hex editing (i get invisible things in game)so i would like to know if there is any other 3d file that it could actually be read by PW
i mean for example if i make a .3ds (or any other 3d file )and rename it to .ski will it read it? or if there is another way for ski files ?

You need to remember to give .ski file correct name, or it will be invisible. Maybe check it out :P

yeh i know abt the name thing i just rename like with any other folder i know i have to do by hex but just cant find which part in the hex is abt the name (hex is still a mistirious thing for me )

Quote:

---

Originally Posted by CULOBG

yeh i know abt the name thing i just rename like with any other folder i know i have to do by hex but just cant find which part in the hex is abt the name (hex is still a mistirious thing for me )

---

Leave the folder name in the ski alone, unless you want to change a bunch of other things. You can use the blender import/export script to edit the models if you want...

Also, make sure your mips are created, if not, then you'll only see things at 1 angle and close, if you go closer or further away, what you did will vanish.

Quote:

---

Originally Posted by das7002

Leave the folder name in the ski alone, unless you want to change a bunch of other things. You can use the blender import/export script to edit the models if you want...

---

yeh eactly what i wanted to do... i want to make a custom weapon i edit the ski file easly but when is up to export from Blender and hex editing i dont know anymore what to do

Quote:

---

Originally Posted by ghostwolf2386

Also, make sure your mips are created, if not, then you'll only see things at 1 angle and close, if you go closer or further away, what you did will vanish.

---

mips? whats that? :O

Dunno how to explain it fully, but it's basically like a mapping system inherent with DDS, where in, it creates miniature sizes of what you are working on, since your working in 3D, space is not a constant, and your view of a subject in that space changes. Where as a regular 2D object is static in space (IE any old Atari game) a 3D object needs to move. With that movement, the viewer will become more in-focus/field-of-view, or lesser, depending on how they are moving. MIPS allows for this, in as, it will adjust the item being viewed according to the distance and position of the viewer.

Now that I have you totally confused, the best way to explain it is like this.... hold you hand in front of you, now, turn from your waist holding you hand even with your line of sight, your hand never changes size, even though your moving (that's what things would look like kinda in 2D) Now, same thing, hold your hand up, but this time, move it away from you, as you see, your hand get's smaller.

MIPS allows for the difference in size when viewing an object in 3D.

Dunno, maybe I confused ya more than before, but as I said, I really don't know how to explain it fully, other than, if you don't use them, depending on what you working on, you'll see what you edited at one distance/angle, but as soon as you move a certain way, it all disappears.

Maybe someone that understand them better can explain it better than me :P

Quote:

---

Originally Posted by ghostwolf2386

Dunno how to explain it fully, but it's basically like a mapping system inherent with DDS, where in, it creates miniature sizes of what you are working on, since your working in 3D, space is not a constant, and your view of a subject in that space changes. Where as a regular 2D object is static in space (IE any old Atari game) a 3D object needs to move. With that movement, the viewer will become more in-focus/field-of-view, or lesser, depending on how they are moving. MIPS allows for this, in as, it will adjust the item being viewed according to the distance and position of the viewer.

Now that I have you totally confused, the best way to explain it is like this.... hold you hand in front of you, now, turn from your waist holding you hand even with your line of sight, your hand never changes size, even though your moving (that's what things would look like kinda in 2D) Now, same thing, hold your hand up, but this time, move it away from you, as you see, your hand get's smaller.

MIPS allows for the difference in size when viewing an object in 3D.

Dunno, maybe I confused ya more than before, but as I said, I really don't know how to explain it fully, other than, if you don't use them, depending on what you working on, you'll see what you edited at one distance/angle, but as soon as you move a certain way, it all disappears.

Maybe someone that understand them better can explain it better than me :P

---

Oh yeah i understood what u mean, but lets say i first wanna focus on exporting the edited weapon so that it works even if only at close range dont think it will create me problems with mips as all i do is edit the already existing weapon...

Hey, didn't want to make a new thread as my question is to do with .ski files.

I have followed the various tutorials and tips on this site, but I still can't get Blender to register that there's an Import or Export script for .ski files.

Did I go wrong somewhere or is it to do with the different versions of Python and Blender I have installed from the ones in the tutorials?
Google didn't throw much up for other .ski file import/exporters.

Quote:

---

Originally Posted by McVinster

Hey, didn't want to make a new thread as my question is to do with .ski files.

I have followed the various tutorials and tips on this site, but I still can't get Blender to register that there's an Import or Export script for .ski files.

Did I go wrong somewhere or is it to do with the different versions of Python and Blender I have installed from the ones in the tutorials?
Google didn't throw much up for other .ski file import/exporters.

---

i am currently using blender v2.49 and phyton 2.5.2 and it works perfectly as guide tells

I have Python 272 and the latest version of Blender from their website. EDIT: that's version 2.58 btw.

Quote:

---

Originally Posted by McVinster

I have Python 272 and the latest version of Blender from their website. EDIT: that's version 2.58 btw.

---

I had last blender and phyton too but didnt work so i sticked with the ones the tutorial said aka the one i wrote up (use those and u shouldnt have any problem)

Hmm I think I've spotted something that's going wrong, the new Blender came with some sort of basic Python and it's probably conflicting. Will go and find the old version and let you know if it works or not :).

Quote:

---

Originally Posted by McVinster

Hmm I think I've spotted something that's going wrong, the new Blender came with some sort of basic Python and it's probably conflicting. Will go and find the old version and let you know if it works or not :).

---

Did you make sure that the script was in the right location? It is rather specific with where they need to be...
Doc:Manual/Extensions - BlenderWiki

Quote:

---

Originally Posted by das7002

Did you make sure that the script was in the right location? It is rather specific with where they need to be...
Doc:Manual/Extensions - BlenderWiki

---

I now have no folders in the Blender directory, so I think I did something horribly wrong. I will try with the latest versions of Blender again, because it seems there are two folders called scripts...

EDIT: The latest version of Blender is not playing ball, but I tried 2.4.9b and it worked to get the script into Blender right away!
BUT, there's always a but... I get a python script error when I try to Import something.

Thanks Das and CULOBG for your help so far.