Fail Compile (macro "gDPSetCombineLERP" requires 17 arguments, but only 3 given)

[Jhair007]

For some strange reason, when I try to compile SM64 (I believe with the required modifications), I get an error saying that I'm missing arguments for "SetCombineMode"/"SetCombineLERP", even though the original "gbi.h" file was structured the same way. I checked the rest of the file, and I think it's almost identical to the original (in the "#define" section). This happened on SM64EX-ALO,.

[sauraen]

Thanks for the report. The errors are a little misleading; the actual problem is that G_CC_ENVIRONMENT is not defined in the GBI. If it was defined correctly, it would expand to 8 arguments, which would ultimately make the outer macro have 17 arguments as it needs. Are you sure this G_CC_ENVIRONMENT is used in vanilla SM64 and not something from a mod?

[Jhair007]

Thanks for the report. The errors are a little misleading; the actual problem is that G_CC_ENVIRONMENT is not defined in the GBI. If it was defined correctly, it would expand to 8 arguments, which would ultimately make the outer macro have 17 arguments as it needs. Are you sure this G_CC_ENVIRONMENT is used in vanilla SM64 and not something from a mod?

If we're talking about the ROM, I use SM64 Vanilla, but if we're talking about the source code, no, it's SM64ex-alo. If that's what you mean.

[sauraen]

I mean, you're trying to build some code which includes G_CC_ENVIRONMENT, which is not defined in the F3DEX3 GBI. Is G_CC_ENVIRONMENT something from vanilla SM64 (e.g. the decomp) or is it something added by whatever hack platform you're using? If it's in vanilla SM64, then it's my bug that it's not in F3DEX3 and I'll have to add it. If it's something custom from one project, I would consider adding it if you send me the link to where it's defined.

[Jhair007]

I mean, you're trying to build some code which includes G_CC_ENVIRONMENT, which is not defined in the F3DEX3 GBI. Is G_CC_ENVIRONMENT something from vanilla SM64 (e.g. the decomp) or is it something added by whatever hack platform you're using? If it's in vanilla SM64, then it's my bug that it's not in F3DEX3 and I'll have to add it. If it's something custom from one project, I would consider adding it if you send me the link to where it's defined.

Now that I'm looking at the image, I'm getting an error in some code. And I haven't modified any of the code (except for the HUD and the Exclamation Box behavior), so could it still be considered vanilla? Since I was only changing ("""IMPROVING""") the textures and 3D models. And I think they were just simple changes, although I also tried to do it in other source codes (without modifying except for the F3DEX3 implementation), but I don't remember what error it indicated.

[Jhair007]

I mean, you're trying to build some code which includes G_CC_ENVIRONMENT, which is not defined in the F3DEX3 GBI. Is G_CC_ENVIRONMENT something from vanilla SM64 (e.g. the decomp) or is it something added by whatever hack platform you're using? If it's in vanilla SM64, then it's my bug that it's not in F3DEX3 and I'll have to add it. If it's something custom from one project, I would consider adding it if you send me the link to where it's defined.

Now that I'm looking at the image, I'm getting an error in some code. And I haven't modified any of the code (except for the HUD and the Exclamation Box behavior), so could it still be considered vanilla? Since I was only changing ("""IMPROVING""") the textures and 3D models. And I think they were just simple changes, although I also tried to do it in other source codes (without modifying except for the F3DEX3 implementation), but I don't remember what error it indicated.

But anyway, I stopped focusing on this microcode a while ago, but thanks for reading anyway.

[sauraen]

3D models on N64 are represented as display lists, which get compiled. They are technically not "code" but static data. Anyway, it's in the process of compiling one of your display lists--which could be one you imported/created, or one in the vanilla game--and this display list includes G_CC_ENVIRONMENT. Please do a search for this in your project, figure out what model it's from, and figure out if that model is vanilla or not.

[Jhair007]

3D models on N64 are represented as display lists, which get compiled. They are technically not "code" but static data. Anyway, it's in the process of compiling one of your display lists--which could be one you imported/created, or one in the vanilla game--and this display list includes G_CC_ENVIRONMENT. Please do a search for this in your project, figure out what model it's from, and figure out if that model is vanilla or not.

Well, I'm starting again with the microcode test. Just tell me how do I install it specifically to SM64? And then I say how it went.

[Jhair007]

Now I'm trying it on ultrasm64 in vanilla and it tells me "warning: missing braces around initializer"

[sauraen]

Please read the documentation for porting a codebase to F3DEX3 https://hackern64.github.io/F3DEX3/porting.html
and the documentation for each of the GBI options https://github.com/HackerN64/F3DEX3/blob/main/gbi.h#L6-L12 .

Note that each individual developer doesn't need to separately port F3DEX3 to a particular codebase. Once it has been done once for that codebase by someone, you can use their work. HackerSM64 already has F3DEX3 support and other projects may have it as well. I'm not a SM64 developer so I don't know in detail.

[Jhair007]

Please read the documentation for porting a codebase to F3DEX3 https://hackern64.github.io/F3DEX3/porting.html and the documentation for each of the GBI options https://github.com/HackerN64/F3DEX3/blob/main/gbi.h#L6-L12 .

Note that each individual developer doesn't need to separately port F3DEX3 to a particular codebase. Once it has been done once for that codebase by someone, you can use their work. HackerSM64 already has F3DEX3 support and other projects may have it as well. I'm not a SM64 developer so I don't know in detail.

I decided to restart the process a second time, and now it says I'm missing the uSprite, which isn't mentioned in the documentation. Can you help me?