phosit
WFG Programming Team-
Posts
84 -
Joined
-
Last visited
-
Days Won
2
Everything posted by phosit
-
An AI was roman.
-
Indeed, thanks for the ping. It should be fixed with rP27994.
-
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
After updating ICU I also had linkage errors. It was fixed by cleaning the workspace. -
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
Looking at the linked ticket a future 2.12.3 should no longer have any issue, still technically it's a downstream bug, just that the fallout was unexpectedly large and the missing headers where injected back upstream. So I'd add the parser header regardless as this also allows the use of all 2.12.x releases. Right i used 2.12.1 Can you upload a patch? (I'm shy of patching libraries) To address the readability issue we could use a temporary/using. using MaybeConstXmlError = std::conditional_t<LIBXML_VERSION >= 21200, const xmlError, xmlError>; void errorHandler(void* UNUSED(userData), MaybeConstXmlError* error) -
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
Thank you for the work. I don't like preprocessor directives. We could go for: void errorHandler(void* UNUSED(userData), std::conditional_t<LIBXML_VERSION >= 21200, const xmlError, xmlError>* error) Also that wouldn't introduce duplication. @hyperion Does Fcollada also have an issue with newer lxbxml2 version? I get this errors: FCollada/FUtils/FUXmlDocument.cpp: In constructor ‘FUXmlDocument::FUXmlDocument(FUFileManager*, const fchar*, bool)’: FCollada/FUtils/FUXmlDocument.cpp:39:39: error: ‘xmlParseMemory’ was not declared in this scope 39 | xmlDocument = xmlParseMemory((const char*) fileData, (int)fileLength); | ^~~~~~~~~~~~~~ FCollada/FUtils/FUXmlDocument.cpp: In constructor ‘FUXmlDocument::FUXmlDocument(const char*, size_t)’: FCollada/FUtils/FUXmlDocument.cpp:67:23: error: ‘xmlParseMemory’ was not declared in this scope 67 | xmlDocument = xmlParseMemory(data, (int)length); | ^~~~~~~~~~~~~~ -
In days of old, when winter's chill did reign, Meat was a luxury, scarce and plain. The frozen fields lay barren, void of life, Leaving hunger pangs to plague our strife. But fear not, for in those frozen lands, There were still ways to feed our hands. We turned to fields of grain and green, Where other forms of sustenance were seen. The wheat and oats we harvested with care, Baked into bread, our bellies could bear. And from the gardens, vegetables galore, Stews and soups we made, and more. In winter's grip, we found a way, To survive each day, come what may. For though meat was a rarity, Our resourcefulness kept us in unity. So let us cherish these fields of gold, That give us life, both young and old. For in their bounty, we find a way, To thrive, even in winter's gray.
-
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
Ok i reinstaled the git repo, but still don't get the xml error. If there is no objection i'll commit it as is. -
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
No, I also use GCC 13.2.1 from the arch repo I'll reinstall the complete git repo this weekend to see if that yields more errors. (Probably ./clean-workspace.sh didn't clean everything) -
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
Curiously i don't get an error about the xml-validator stuff. I made a patch about thous errors I get. @Riesi I added you as "Riesi" to the credits. Is this ok for you? Do you also want your name? -
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
sure -
Building latest revision is currently broken for Linux
phosit replied to Riesi's topic in Applications and Contributions
I also use Linux. I didn't encounter this error untill you mentioned it. I don't get it all the times. Propably it's because of the precompiled header. We already use CI. -
The OPEX cost would make the popcap a less hard limit. Which is good IMO.
-
I like how the cities integrate in to the terrain. In 0 A.D. the maps who have cities protected by cliffs are mainly acropolises. Which look unnaturally exposed.
-
It's likely the same error as this one: https://wildfiregames.com/forum/topic/95151-i-dont-know-what-to-do-can-someone-help-me-and-explain
-
Thank you for all your time. You always had the overview but still commented on many small things. I apreciated that.
-
Random map way too random when created in the Editor...
phosit replied to krt0143's topic in Game Modification
Why do you always write statements that contradict itself... Did you generate a "Survival of the Fittest" before? Then it could be due to this bug. I'm working on such a diff (Not the whole map will be flooded) -
"Elephantine" map - How do you get across the Nile?
phosit replied to krt0143's topic in General Discussion
I don't know what's the cause. Propably there is now less space for the Kushite units... Did you just smooth the shorelines or did you also add a tree? -
"Elephantine" map - How do you get across the Nile?
phosit replied to krt0143's topic in General Discussion
It's not commited yet. I expect it will be commited untill a27. -
"Elephantine" map - How do you get across the Nile?
phosit replied to krt0143's topic in General Discussion
To take advantage of the patch you have to get the development version and apply the diff or make a mod out of it. -
"Elephantine" map - How do you get across the Nile?
phosit replied to krt0143's topic in General Discussion
That's what D5136 tries to do. Doesn't it work for you? -
Question: Headless Replays
phosit replied to Dizaka's topic in Game Development & Technical Discussion
Do you mean "non-visual-replays", started with "./pyrogenesis --replay=<path_to_commands.txt>" ? The code is in "source/ps/Replay.cpp". -
AI Behavior (surrendering, taunting, strategy, etc.)
phosit replied to wowgetoffyourcellphone's topic in Gameplay Discussion
Oh, and there is #2344 which also uses the word "persoality" but with a different notion.