-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
FSX Any Ideas On This Error
- Thread starter cdogg
- Start date
- Messages
- 34
- Country
-
I was hoping that wasn't the problem but... I have 162 textures. 27 ground poly's, each with a HW/LM/SP/SU/FA/WI. I guess if that is the case I can use the summer texture for both Spring & Summer, but I'd rather not have to.
Thanks,
-Chris-
EDIT: Just removed the entire spring season and re-coded everything. still receiving the error; minus spring I have 135 textures. So either I need to split my ground poly's into 2 BGLs, get rid of some more seasons, or the error I'm getting is totally unrelated and I'm following a rabbit trail! lol
Thanks,
-Chris-
EDIT: Just removed the entire spring season and re-coded everything. still receiving the error; minus spring I have 135 textures. So either I need to split my ground poly's into 2 BGLs, get rid of some more seasons, or the error I'm getting is totally unrelated and I'm following a rabbit trail! lol
Last edited:
- Messages
- 32,883
- Country
-
Hi,
I had another look at the BGL opcodes, and I don't think you have a problem with the amount of textures yet. That is only after about 800 texture entries if I calculated it right.
You only have 270 textures so that should be fine (the night texture needs to be defined for every seasons, since it is a subtexture type).
So I had a look at the code and it seems the problem is with the IFIN1 command. This command can only jump over 65536 bytes of code, I think you have too many polygons for this command to jump over.
To get around that you would need to restructure the entire code. Maybe it is easier than to export as two files.
Btw, I am working on tool support for ground polygons, so that in the future ASM tweaking to get seasons is no longer needed.
I had another look at the BGL opcodes, and I don't think you have a problem with the amount of textures yet. That is only after about 800 texture entries if I calculated it right.
You only have 270 textures so that should be fine (the night texture needs to be defined for every seasons, since it is a subtexture type).
So I had a look at the code and it seems the problem is with the IFIN1 command. This command can only jump over 65536 bytes of code, I think you have too many polygons for this command to jump over.
To get around that you would need to restructure the entire code. Maybe it is easier than to export as two files.
Btw, I am working on tool support for ground polygons, so that in the future ASM tweaking to get seasons is no longer needed.
- Messages
- 32,883
- Country
-
Hi Chris,
Another idea would be to do the season check around the MATERIAL command only and not around the DRAW_TRI_LIST command. That will keep the jumps smaller, but would mean you have slightly more checks.
Another idea would be to do the season check around the MATERIAL command only and not around the DRAW_TRI_LIST command. That will keep the jumps smaller, but would mean you have slightly more checks.
- Messages
- 32,883
- Country
-
Hi Chris,
If all polygons with a certain material are at the east or west, then splitting like that will not work indeed.
What I suggested is that you put the IFIN to check for the different season around each MATERIAL command. So you choose for each material assignment the right one based on the season. The triangles are just always drawn with the same code.
That how the code sample on the Wiki tutorial looks.
If all polygons with a certain material are at the east or west, then splitting like that will not work indeed.
What I suggested is that you put the IFIN to check for the different season around each MATERIAL command. So you choose for each material assignment the right one based on the season. The triangles are just always drawn with the same code.
That how the code sample on the Wiki tutorial looks.