v 26, and above ALL Bugs/Crashes reporting thread

Alright guys I'm on it... very confusing. I had this issue, then I didn't, now I do again... how odd. I wonder if it was due to an overwrite that took place on those schemas when I updated just before a push? huh... anyhow, I'm fixing it now and it shouldn't take me long.

EDIT: I'm looking over these schemas and promotionlineinfo files that are showing errors and I'm not seeing any cause for it to be presenting these errors!!! Very confusing... is there anything I'm missing here???
 
Ok... I've exhausted everything I know to look for. I'm looking in the dll at this point and I'm still confused as to why this is taking place. But my going theory is that I may have overlooked a step in setting up PromotionLineInfos for being properly utilized within a module.

So, while I'm going to state that I have this problem and request some assistance sorting it out as it will become a bigger problem down the road, I'm going to see if I can't just add the Promotionlines I'm defining for those modules into the core PromotionLineInfos and just eliminate the module PromotionLines.

EDIT: Nope... I still have the schema ignoring the tag <PromotionLine> in the module schema, even though its there and that schema is an exact duplicate of the core schema with the new name.

In short... I'm stumped and really hoping someone can help!
 
Hydro helped me figure out what was wrong... and it was something I didn't realize about modularization and schemas. Lesson now learned and as a result, I am less a noob today than yesterday ;)

I'm just waiting on an answer from Hydro as to whether he wants me to help him with the fix or not since all his unit schemas now require updating to the current core schema.
 
Hydro helped me figure out what was wrong... and it was something I didn't realize about modularization and schemas. Lesson now learned and as a result, I am less a noob today than yesterday ;)

I'm just waiting on an answer from Hydro as to whether he wants me to help him with the fix or not since all his unit schemas now require updating to the current core schema.

I wonder then IF i have to do that to all my schema's? :hmm:

Well i am off for a long nap, see you'll later, or write you'll later, which ever :crazyeye:
 
Not yet. But its probably not a bad idea to update building and unit schemas since the combat mod went into place. Though there's still some adjustments and tweaks yet so if you'd like me to wait and let you know when I've stabilized enough to do so without expecting to have to turn around and do it again in a week, I'll hold off on blowing the whistle til I think its ready for that.

I really hadn't intended to require all those DH and Hydro schemas to update all at once like that but its really unavoidable at this step as I put the promo lines in for those modularized promos that deserved it. If we gave each module its own schema names it would reduce the amount of work that comes up on a pointed schema update though.
 
Not yet. But its probably not a bad idea to update building and unit schemas since the combat mod went into place. Though there's still some adjustments and tweaks yet so if you'd like me to wait and let you know when I've stabilized enough to do so without expecting to have to turn around and do it again in a week, I'll hold off on blowing the whistle til I think its ready for that.

I really hadn't intended to require all those DH and Hydro schemas to update all at once like that but its really unavoidable at this step as I put the promo lines in for those modularized promos that deserved it. If we gave each module its own schema names it would reduce the amount of work that comes up on a pointed schema update though.

Modules are a little weird, you need to talk to DH/Hydro and Koshling more on that stuff, but if Hydro isn't back in 15 minutes do what ever you need to and we'll worry about it (well) today!:)
 
Modules are a little weird, you need to talk to DH/Hydro and Koshling more on that stuff, but if Hydro isn't back in 15 minutes do what ever you need to and we'll worry about it (well) today!:)

Hmmm? I thought TB solved it now. And yes its a known issue if you have schemas with the same name then they must all be exactly the same. Thus you can either name them all a different name or keep them all the same.

This is why say old buildings/units can still have old schemas since they often have their own name and don't have any new tags thus not needing to update. However if you plan to add to the file its good to update. Otherwise you may run into an undefined tag because you never updated the schema. Which is exactly what happened when TB added stuff to our files. And in turn since other mods had the same name they also needed to be updated.
 
Hmmm? I thought TB solved it now. And yes its a known issue if you have schemas with the same name then they must all be exactly the same. Thus you can either name them all a different name or keep them all the same.

This is why say old buildings/units can still have old schemas since they often have their own name and don't have any new tags thus not needing to update. However if you plan to add to the file its good to update. Otherwise you may run into an undefined tag because you never updated the schema. Which is exactly what happened when TB added stuff to our files. And in turn since other mods had the same name they also needed to be updated.

:hmm: I guess thats why i was told three years ago or more to re-name them for EACH folder separate, heck i cant even remember his name but he had something to do with the original modules.

And the answer to your question that was at 1 a.m.ish when i wrote that, and hence then TB got it working correctly.:p
 
Hmmm? I thought TB solved it now. And yes its a known issue if you have schemas with the same name then they must all be exactly the same. Thus you can either name them all a different name or keep them all the same.

This is why say old buildings/units can still have old schemas since they often have their own name and don't have any new tags thus not needing to update. However if you plan to add to the file its good to update. Otherwise you may run into an undefined tag because you never updated the schema. Which is exactly what happened when TB added stuff to our files. And in turn since other mods had the same name they also needed to be updated.
Another option is actually not to refer to a schema in the XML.
 
I suspect this was addressed by a fix TB made last night.

You noticed that tiny tweak huh? lol... it wasn't compiled though. Just a source update for the next compile.
 
Something else I noticed: with viewports off and a Wonder Movie starting, the camera centers on the city that just built the triggering Wonder. With Viewports on, the camera will zoom to the city building the Wonder if the city is on the current viewport, but won't recenter on that city and won't switch to a city that is off the current viewport (it just plays the movie). I think that the viewport should always switch and center on a city building something that triggers a Wonder.
 
oh. In that case my push this afternoon will include it if you dont do one first
My internet is very slow with pushes on the SVN, particularly with the dll archive (takes about an hour) so I'm reluctant to compile after such a small tweak. I'm probably not doing much programming today (maybe one thing though) so yeah, either way.
 
Back
Top Bottom