FF051 OoS thread.

are you getting it to connect with the disc in the tray? I have been playing without the disc since the 3.19 patch on ffh2.
 
Ouch. Well, then I hope it's not early; is it a high school or lower test? XD Then I can help you.

Anyway, I tested things out some, and with both the Amurites and Scions to see if it was just the Amurites for some odd reason.

Any temporary summoned unit, it seems (tested with fireballs, fire elementals, wraiths, specters, and skeletons) will increase unit supply costs when they attack and die. Fireballs will increase it if they attack and win, because they die instantly. The other temporary summons do not increase it any when they attack and win, because they didn't die from it.

Skeletons, however, being permanent summoned units did not increase the unit supply costs upon death.

I also tested it with FFH2 041D, and it did not increase it any, so it must be a problem with Fall Further.
 
Interesting it only happens with temporary ones, I figured it would happen with all summons. And no, the test isn't High School level (I would pray nobody is preparing for one of those and a child, but I realize it happens). It is for my Masters degree.
 
Mmm, I'm only working on my Associates degree, so I probably can't help you any with that. Oh well. Hope you do well...

The only difference I know in how summons are handled in FF from FFH is the Caster/slave system... Perhaps the problem is in there? Other than that I have no ideas, unfortunately.
 
Don't worry, I'm pretty sure I know where the problem is, I just have to set up a debug DLL and run through the code on it. There are some pretty hefty differences in how we handle summons from base FfH, I believe that this particular issue is from Kael starting to handle them similar to how we do. I attempted to omit all of his changes as they were redundant, but probably missed one, or reverted improperly in some section.
 
Going out of synch all the time with my friends in multi. IS there a better way to get the game to resynchronize than to save it and have EVERYONE reconnect? If just one person ever crashes and resumes, the whole game goes oos again and nothing is gained... it's very frustrating..
I have a lot of OOS logs in the bts folder (most recents are turn 331, 332, 333, 334, 335, 336....)
they look like this

-----------------------------------------------------------------
-----------------------------------------------------------------
GLOBALS
-----------------------------------------------------------------
-----------------------------------------------------------------


Next Map Rand Value: 888
Next Soren Rand Value: 7735
Total num cities: 54
Total population: 260
Total Deals: 3
Total owned plots: 952
Total num areas: 7


-----------------------------------------------------------------
-----------------------------------------------------------------
PLAYER 0: Deus
 
yes, I broke the logger with a change I tried to make last release. My laptop cannot handle running 2 instances anymore, and it was a small change, so I had included it untested.

No way to clear an OOS except having the person who has a different number rejoin, and you cannot have just a single person rejoin in FfH without causing errors. So save and out to lobby for everyone is the only option.
 
So, in other words, I can't send any OoS logs and have them do any good right now?

Also, I've been wondering for a long time why that was, and why it hasn't been fixed yet. I assume that it can't be fixed for whatever reason, but... You never know with some of these things.

About the fireball/summon thing, though... Any idea what files it'd be in? Because I'm willing to take a look at them and see if I can find any painfully obvious causes. I'm actually reasonably good at interpreting programming, just not good at remembering how to do the stuff in it or knowing precisely how something works.
 
Interesting to note... I've been semi-forced to cast fireball (via firebows, if it matters) in my FF+ game, while defending my cities, and it seems that if they die in your territory they don't add to the unit supply... I'll have to test that more thoroughly, though.

Edit: For the record, I did test earlier about the summons raising the supply in FF+ earlier (before any of the added fixes or modules) and they did, but that was attacking into enemy territory or unowned territory.
 
Well Xien... any idea if you'll fix it in the nearer term or the latter term? Just to have some kind of idea
 
submitting logs now is always good. it just means that they'll sit in a pile quietly until they're ready to be worked on, rather than xienwolf finding the time to work, and having no logs to do stuff with.
 
So far my current version, I've only had one OOS because I didn't upgrade my own module when I upgraded the version I sent out >_> but for all FF core functions I haven't seen an OOS since I removed the Kuriotates from the AI being able to play them.

Sadly, at this point it may be the best option - me and my buddies have been struggling to keep games OOS free, but whenever the Kurio show up it's an inevitable road to problem after problem.
 
Right now, there is no use in posting logs because I broke the logger with one of my upgrades, most likely in Patch B only, but prior patch logs aren't too useful anyway, so basically it is useless atm.

I just finished my exams for my Master's, so I should have free time to return to debugging soonish. I put a LOT of other things on the back burner while I was studying as well though, so it might be a while till I work miracles, but at the least I should be able to solve the fireballs and restore the logger.
 
Lucky you people, I get an OoS with pretty much every multiplayer game I play, with the exception of those that last </= 20 turns.

"yes, I broke the logger with a change I tried to make last release." is what I meant when I asked if it's pointless to send OoS logs. If the logger is broken, then what's the point?

Edit: Oooh, posted while I was reading the posts. Anyway, how'd the exams go? ^_^ Welcome back, by the way.
 
BTW, Xien, would you like me to post up my changed OOSLogger python code for everybody?

We're able to get full OOS logs from it now.
 
Allright. If everybody in the group replaces your OOSLogger.py file, in Fall Further 051/assets/python, you'll be able to generate useful OOS logs for Xien.
 

Attachments

Back
Top Bottom