Hi I just converted a truck from 3DS, however, when I spawn it in FiveM, this error came up "Invalid fixup address is neither virtual nor physical"
Attached are some of my Zmod nodes, I think this is the cause but I am not really sure.
Any help/suggestion is highly appreciated.
Many thanks.
[HELP] Invalid fixup address is neither virtual not physical
-
- Posts: 8
- Joined: Mon Mar 28, 2022 7:06 am
Re: [HELP] Invalid fixup address is neither virtual not physical
what is the .yft file size of you get after an export?
-
- Posts: 8
- Joined: Mon Mar 28, 2022 7:06 am
Re: [HELP] Invalid fixup address is neither virtual not physical
hmm.. have you tried to re-import model back into ZModeler to check whether hierarchy is OK? I can see a set of custom names that I haven't seen on original models (yet may be these are correct names as I assume this is a truck or a trailer mod?). As a quick test, try to remove some parts like "legs", "dq", "shinies", "Tuthodien"... may be one of these parts causes problems.
Other than that - does your model work fine in game in story mode? (not via FiveM server).
Other than that - does your model work fine in game in story mode? (not via FiveM server).
-
- Posts: 8
- Joined: Mon Mar 28, 2022 7:06 am
Re: [HELP] Invalid fixup address is neither virtual not physical
Ah thanks, it worked by removing "tuthodien" and "engineblock"Oleg wrote: ↑Mon Mar 28, 2022 7:38 am hmm.. have you tried to re-import model back into ZModeler to check whether hierarchy is OK? I can see a set of custom names that I haven't seen on original models (yet may be these are correct names as I assume this is a truck or a trailer mod?). As a quick test, try to remove some parts like "legs", "dq", "shinies", "Tuthodien"... may be one of these parts causes problems.
Other than that - does your model work fine in game in story mode? (not via FiveM server).
I supposed it is due to the custom names/file size (reduced from 11.4 to 4.96MB), but I have used many custom names in the past, so I am not sure why this particular problem occurred.
Thanks for the suggestion.
Re: [HELP] Invalid fixup address is neither virtual not physical
try to rename them, but keep parts available. Also, you can attach parts one to another when you don't need the part to act on its own. For example, quite a lot of things could be attached to "chassis". If part exceeds 64K vertices, use "group" instead of attaching.
-
- Posts: 8
- Joined: Mon Mar 28, 2022 7:06 am
Re: [HELP] Invalid fixup address is neither virtual not physical
Yeah I grouped both "tuthodien" and "engineblock" because of their high vertices.Oleg wrote: ↑Mon Mar 28, 2022 8:10 am try to rename them, but keep parts available. Also, you can attach parts one to another when you don't need the part to act on its own. For example, quite a lot of things could be attached to "chassis". If part exceeds 64K vertices, use "group" instead of attaching.
Removing them worked but im not really sure why it occurred in the first place? Perhaps due to grouping them together? Going to try ungroup and split them up/rename when im home.
-
- Posts: 8
- Joined: Mon Mar 28, 2022 7:06 am
Re: [HELP] Invalid fixup address is neither virtual not physical
I have to separate the high polycount into a second file (grill, for example). Can't get them to work together in a single file even though the limit is not yet exceeded (group/ungroup both didn't work). A fix for anyone with the same problem.