21.04.2009, 15:05
I've not had much luck.
Working with Muas, we've added a new slot at the bottom of the 'FIELDS' list and changed the array from 32 to 33.
No luck.
I think the problem may be that the engine is designed to assign road and rail textures to all RGB values above 31 on map_t. Every single RGB value is taken by road and rail. So, by adding a extra line calling for the texture to use RGB 32, it achieves nothing.
I'll keep looking, but I don't want to get too distracted from my map. I have other ideas for creating custom unique airfields that don't require new texture slots and work, but it would certainly be nice to crack the texture slot problem. I'm not sure if the 352nd actually have managed to introduce new slots. They're very cagey about saying if they have, so perhaps they're actually using a standard number of texture slots but have different load.ini for different versions of the map (i.e a load.ini if you're flying over England and a different load.ini for flying over France. )
Joe
Working with Muas, we've added a new slot at the bottom of the 'FIELDS' list and changed the array from 32 to 33.
No luck.
I think the problem may be that the engine is designed to assign road and rail textures to all RGB values above 31 on map_t. Every single RGB value is taken by road and rail. So, by adding a extra line calling for the texture to use RGB 32, it achieves nothing.
I'll keep looking, but I don't want to get too distracted from my map. I have other ideas for creating custom unique airfields that don't require new texture slots and work, but it would certainly be nice to crack the texture slot problem. I'm not sure if the 352nd actually have managed to introduce new slots. They're very cagey about saying if they have, so perhaps they're actually using a standard number of texture slots but have different load.ini for different versions of the map (i.e a load.ini if you're flying over England and a different load.ini for flying over France. )
Joe