User Pass
Home Sign Up Contact Log In
Page:
 
islander1
offline
Link
 
Originally posted by SAGA45
Is anything being done about this?


I hope so. Maybe Bort can seperate the general section for one sheer, and conditionals/quarter based ones onto a second (and just read the quarter based ones first).

Defensively, I think something ELSE might be in play, because my defensive AI in sheer size is perhaps 60% of the size of my functional offense now. I'm troubleshooting and testing as I can now...and praying my base defense from a few days ago holds for my team in the meantime.
 
Mike1709
offline
Link
 
I've cut my 4th quarter settings down to about 60% of what it was (which was about 75% of the total playbook) and haven't had any trouble since *touch wood* other than the top 2 inputs in the 4th Q settings swapping round, nothing missing though.
 
Link
 
bump
 
Bort
Admin
offline
Link
 
Hm...I've been trying to come up with a good scheme to approach giant AI's, but nothing easy has jumped out at me. I'm thinking at this point that whatever I do will probably require an entire rewrite of the saving mechanism to save one or two items at a time via AJAX. Guess that will be next on my list.
Last edited Nov 16, 2008 20:07:30
 
Bort
Admin
offline
Link
 
Ok, I have a question, so I'm not confused as to what I'm looking for:

Are you losing inputs/outputs when saving a preset, or when hitting "update" to just save your settings? Big difference as to where to look.

The more I read, I think it's got to be when saving/loading presets. Am I right? If so, we might be hitting the limit on MySQL's blob field size and I need to choose a larger field type.
Last edited Nov 16, 2008 20:49:17
 
islander1
offline
Link
 
Originally posted by Bort
Ok, I have a question, so I'm not confused as to what I'm looking for:

Are you losing inputs/outputs when saving a preset, or when hitting "update" to just save your settings? Big difference as to where to look.

The more I read, I think it's got to be when saving/loading presets. Am I right? If so, we might be hitting the limit on MySQL's blob field size and I need to choose a larger field type.


I am 80% sure it happens in both scenarios, Bort. I wish I could say it happens in one case or the other...but if you hooked me up to a polygraph I'd say both instances. I am 100% sure of the saving/loading option. The update I am pretty sure it occurs also, but it's hard for me to, thinking back, separate clicking the update button versus saving as I do both so much :/

I can try and pay close attention moving forward if saving/loading does it. Once I fix my current defense AI (again) I'll make a backup copy of it specifically and fool around with it.
Last edited Nov 16, 2008 20:57:34
 
UnsaidPlayer
offline
Link
 
Originally posted by Bort
Hm...I've been trying to come up with a good scheme to approach giant AI's, but nothing easy has jumped out at me. I'm thinking at this point that whatever I do will probably require an entire rewrite of the saving mechanism to save one or two items at a time via AJAX. Guess that will be next on my list.


Would any of this be a problem I seen today on my team?

2nd quarter 26 seconds left, 0 time outs ball on the opps 28 yard line. We end up running it.

When I checked the play on OAI test it came back at 100% FG.

Our kicker has attempted one just as long already this season.
 
Bort
Admin
offline
Link
 
Originally posted by UnsaidPlayer
Originally posted by Bort

Hm...I've been trying to come up with a good scheme to approach giant AI's, but nothing easy has jumped out at me. I'm thinking at this point that whatever I do will probably require an entire rewrite of the saving mechanism to save one or two items at a time via AJAX. Guess that will be next on my list.


Would any of this be a problem I seen today on my team?

2nd quarter 26 seconds left, 0 time outs ball on the opps 28 yard line. We end up running it.

When I checked the play on OAI test it came back at 100% FG.

Our kicker has attempted one just as long already this season.


No, that would be unrelated to this particular thread. Make sure the settings you put into the tester are complete (including score, timeouts remaining, etc). Also, your kicker could have been tired, so just outside of FG range, etc. That's one that's come up before and that's usually the case.

As for the bug in the OP, I can only think of it happening when saving a preset. I've just tested doing a POST of 500 inputs and they all saved. However, when saving a preset, it would be bigger than the current field length allowed for presets, so it would get truncated.

I'm going to do a 5-10 minute downtime late tonight to update the field type to a larger size and we'll see if the problems go away. Of course, anything already saved that was too long would be truncated and lost, but new saves should work properly after that unless you have 50,000 inputs or something.
 
islander1
offline
Link
 
Originally posted by Bort


As for the bug in the OP, I can only think of it happening when saving a preset. I've just tested doing a POST of 500 inputs and they all saved. However, when saving a preset, it would be bigger than the current field length allowed for presets, so it would get truncated.

I'm going to do a 5-10 minute downtime late tonight to update the field type to a larger size and we'll see if the problems go away. Of course, anything already saved that was too long would be truncated and lost, but new saves should work properly after that unless you have 50,000 inputs or something.


Good deal. I hope this resolves it. You can be sure I will let you know in a couple days, LOL. My offensive AI definitely comes close to 500 inputs+outputs. defense not so much, but again, that was beginning to get truncated as well. That was at, maybe 250? total In + Out

 
UnsaidPlayer
offline
Link
 
Originally posted by Bort
Originally posted by UnsaidPlayer

Originally posted by Bort


Hm...I've been trying to come up with a good scheme to approach giant AI's, but nothing easy has jumped out at me. I'm thinking at this point that whatever I do will probably require an entire rewrite of the saving mechanism to save one or two items at a time via AJAX. Guess that will be next on my list.


Would any of this be a problem I seen today on my team?

2nd quarter 26 seconds left, 0 time outs ball on the opps 28 yard line. We end up running it.

When I checked the play on OAI test it came back at 100% FG.

Our kicker has attempted one just as long already this season.


No, that would be unrelated to this particular thread. Make sure the settings you put into the tester are complete (including score, timeouts remaining, etc). Also, your kicker could have been tired, so just outside of FG range, etc. That's one that's come up before and that's usually the case.

As for the bug in the OP, I can only think of it happening when saving a preset. I've just tested doing a POST of 500 inputs and they all saved. However, when saving a preset, it would be bigger than the current field length allowed for presets, so it would get truncated.

I'm going to do a 5-10 minute downtime late tonight to update the field type to a larger size and we'll see if the problems go away. Of course, anything already saved that was too long would be truncated and lost, but new saves should work properly after that unless you have 50,000 inputs or something.


Thanks Bort.
 
SAGA45
offline
Link
 
Originally posted by Bort
I'm going to do a 5-10 minute downtime late tonight to update the field type to a larger size


Sounds great! Hope it works

 
Bort
Admin
offline
Link
 
Originally posted by SAGA45
Originally posted by Bort

I'm going to do a 5-10 minute downtime late tonight to update the field type to a larger size


Sounds great! Hope it works



Haha, so do I. I have a sneaking suspicion it's the culprit.
 
OUTLAW77
offline
Link
 
I hope so......still sucks to lose all that time and effort, but any improvement we be awsome.
Last edited Nov 16, 2008 21:21:16
 
peacebringer
offline
Link
 
Originally posted by Bort
Ok, I have a question, so I'm not confused as to what I'm looking for:

Are you losing inputs/outputs when saving a preset, or when hitting "update" to just save your settings? Big difference as to where to look.

The more I read, I think it's got to be when saving/loading presets. Am I right? If so, we might be hitting the limit on MySQL's blob field size and I need to choose a larger field type.


definitely saving and loading, or saving what you think is correct, loaded for game and wrote over or deletes some inputs.



 
islander1
offline
Link
 
Originally posted by Bort
Originally posted by SAGA45

Originally posted by Bort


I'm going to do a 5-10 minute downtime late tonight to update the field type to a larger size


Sounds great! Hope it works



Haha, so do I. I have a sneaking suspicion it's the culprit.


Well, I'm definitely optimistic. You seem pretty sharp at this coding business
 
Page:
 


You are not logged in. Please log in if you want to post a reply.