Started by Ranran, August 08, 2022, 09:05:08 AM
0 Members and 1 Guest are viewing this topic.
QuoteEarlier I tried to build a theme .pak using a makeobj-extended that I built myself, I get a ton of warnings about unknown objects.
Quote from: Ranran on September 16, 2022, 08:29:53 AM@Matthew I can assure you that your guess is completely wrong. Your approach to updating makeobj makes absolutely no sense.
QuoteBecause that patch doesn't involve any changes to Makoobj(=object writer), theme object creation for extended should work fine even with standard's makeobj. The change in the patch is that unique icons that were previously output as the same attribute as the season icon have been changed to the same attribute as the theme parts (eg the button that closes the window), makeobj does not need to be changed. Just change the attributes of the object in the dat file. The point is whether the defined object can be read by Simutrans(=object reader). Strictly speaking, reading with reader will not be a problem. because makeobj is not changed. It is important that it is "registered" correctly. That means the symbol must be registered as one of the theme objects. Although themes for extended can be read in standard, extended unique symbols are not registered, so it cannot be seen in the game, but there is no possibility of preventing it from booting.
QuoteThe writer hasn't changed, and judging by the fact that the correct theme I created works, the reader is working as well. So, as I have said many times before, the theme currently distributed on the download server is still old, and I think that the file is not generated or the old file is just copied from simutrans folder.
QuoteThe error indicates that it can't even find images of old theme objects, which means it's your problem.
Skipping unknown object
printf("Skipping unknown %s object %s\n", type, name);
Warning: andard look: Entry "#=Image=> button.0.7" ignored (check spelling)
dbg->warning( obj_writer_t::last_name, "Entry \"%s=%s\" ignored (check spelling)", i.key, i.value.str );
Quote from: Matthew on September 16, 2022, 03:02:54 PMBut I'm not certain that the problem is being unable to find the images. The error messages don't clearly say that, do they? It looks to me as though the error message is itself broken.