[Guest]

ok Fatduck - give me a little time & i will try to write a more complete explanation of how the game is structured - this should help you understand things a little better - give me until the end of today to write it. Its going to take me some time to do btw do you happen to have Teamspeak lol !

[Guest]

ok when i said change gun position what i meant was i would change the name of a mesh file & then change the texture/mat names within the msh file using a hex editor, so that i could get the mesh to use a different texture / mat file. This would mean i would have a new mesh file that i could enter into the 'heir.him' file - but the heir.him file would still use the rest of the files contained within the relevant cockpit position

ok...
fatduck - im real busy tonight so Hellzone is going to explain to you how the game is structured so it will help you understand what the hell im talking about.

First read Hellzone's post then look into this MOD & look into 3do\Cockpit\Pe-3bis & you will see where ive hex edited the meshes to use diffrent files / file names.
(The link is inoperative) /BLENHEIM-4.rar

Hellzone will be posting later on here tonight - stay tuned

[Hellzone]

Ok basicly most of the game is ran by java. "Java Classes"

Each java class contains info like Model location, Paint Schemes, Weapon hooks, Collision info, Tailhook instructions, Wingfold, gear and alot more.


Models consist of a few things, Him, mat "material" msh "model" and TGA's

The hier.him is a file with coordinates to where the models go.


Some Planes have Multiple Model Folders. This is called a Nationality

Nationalitys for example GB is RAF, RAAF and RN. Usa is USMC, USN, USAAF. RU is for russian. JA is for japan and so on. If you have a aircraft that does have 2 folders and you edit one it will not effect all Nationalitys only the one you edit. For Example i change the GB folder and add a tail hook to the aircraft, that means that tail hook will only apply to the RAAF,RAF and RN

If there is a value.. or Txt in the hier.him that does not belong usualy the aircraft will refuse to load, and will give u a error. "Error Hier.him could not be loaded" This usualy only happens if your trying to add a line or one got duplicated.

Example.

[CF_D0]
Mesh CF_D0
Parent _ROOT_
Attaching 0 1 0 -1 0 0 0 0 1 -0.62727 0.00209 0.14734
CollisionObject xcf1
CollisionObject .xxmgun01
CollisionObject .xxammor
CollisionObject .xxmgun02
CollisionObject .xxammol
CollisionObject .xxcontrols3
CollisionObject .xxtank3

[CF_90]

[Guest]

i hope thats ok for you fatduck if its not id be happy to explain further in more detail

[fatduck]

It's not OK!
The files Hellzone is talking can't be found in the demo! Actually no msh, hir files in the demo. Seems they pack inside sfs! I have no files to follow!

Make it simple, basicually you are editing the hir file to change the useage of different msh.
And because sometime inside the msh, there is a external file link to different msh. So you can also hex-edit those external link to use different msh part!
Am I right?

I don't really understand what Hellzone siad about

_WingTipL
_NavLight0

What can you do? what had you done?

Thanks

[RAF_Magpie]

MrJolly - you have PM...

[Guest]

hiya fatduck! so sorry m8 !
its becasue you cant actually mod the demo version

please chk your pm i think we have a solution for you

Make it simple, basicually you are editing the hir file to change the useage of different msh.
And because sometime inside the msh, there is a external file link to different msh. So you can also hex-edit those external link to use different msh part!
Am I right?

YES ! you are right !

please chk your pm

[Hellzone]

The problem is, the demo dosent have filenames that are in filelist.txt.
SFS extractor wasent ment for the demo. but if you need to work with the demo then i will look into it right now for you.

and what i meant by

_WingTipL
_NavLight0

is that thos are hooks. A hook is something like where the wingsmoke comes out, or where a nav light attaches to. Landing lights too. It also is for cannons and guns. Bomb attachment places, booster engines and a few other things.

[fatduck]

and what i meant by

_WingTipL
_NavLight0

is that thos are hooks. A hook is something like where the wingsmoke comes out, or where a nav light attaches to. Landing lights too. It also is for cannons and guns. Bomb attachment places, booster engines and a few other things.

What I really want to know is:
Are these (_WingTipL and _NavLight0) external link to other mesh?
Have you ever change it to get another look?

And what does mean?

[Guest]

and what i meant by

_WingTipL
_NavLight0

is that thos are hooks. A hook is something like where the wingsmoke comes out, or where a nav light attaches to. Landing lights too. It also is for cannons and guns. Bomb attachment places, booster engines and a few other things.

What I really want to know is:
Are these (_WingTipL and _NavLight0) external link to other mesh?
Have you ever change it to get another look?

And what does mean?

no these do not link to other meshes (_WingTipL and _NavLight0) - we have never needed to change these - i dont know what is ?

_WingTipL and _NavLight0 < these are hooks that the class files look for

[Guest]

using this teqnique ive managed to remove the cannon bulges from the spitfire wing for the Mk1 spit - luckily the bulges were seperate meshes withiin the main wing mesh & so i could easily erase them using the mthod we've talked about here

[Hellzone]

WOOT +1 !! Talk to u Tomorrow about it.
Btw congrats

[Radoye]

using this teqnique ive managed to remove the cannon bulges from the spitfire wing for the Mk1 spit - luckily the bulges were seperate meshes withiin the main wing mesh & so i could easily erase them using the mthod we've talked about here

Pictures, we want pictures!!!

[Guest]

SpitMk1 now released without wing bulges !

[MICHOO]

SpitMk1 now released without wing bulges !

I just hope that you has not threw it out on garbage.

Maybe you can take these bulges and stick them on the top of Griffon engine

I'm only joking of course :mrgreen:

Great work !