View Full Version : Long standing Bug
Yossarian
11-23-2003, 03:36 PM
This one has been about FOREVER.
And it bugs me.
When calling your own plays, if you have a guy playing out position (like a RB at WR) due to injuries or whatever, clicking on 'view' causes the game to crash.
Dutch
11-23-2003, 04:13 PM
Hmmm, that sounds like a bug that needs to be brought to Jim's attention. If nobody mentions it, it probably won't be fixed. You can e-mail him at support AT solecismic.com for best results. Here on the boards it's hit and miss.
korme
11-23-2003, 04:25 PM
I clicked on view once, and FOF crashed, and I didn't know why. I think this is the reason.
thomkev22
11-24-2003, 12:51 AM
this has happened to me a few times as well. I didn't realize it was out of postion players causing it, but upon further review that is the case.
Yossarian
11-24-2003, 04:21 AM
I didn't know that nobody was aware of it.
its been bugging (arf arf) me since FOF 4
It also happens when you have out of position players and hit depth chart in the playcalling screen.
Normally, i limit my use of 'depth' or 'view' for those instances where I don't have a player out of position but sometimes that a large part of my offense (Injury cover) or sometimes a starter gets hurt without me being aware of it and....
Francis_Cole
11-24-2003, 06:52 AM
ahh. I have logged before about pressing view causing the game to crash, but I didn't realise it was because of this..
:)
Pumpy Tudors
11-24-2003, 09:01 PM
Originally posted by Yossarian
I didn't know that nobody was aware of it.
its been bugging (arf arf) me since FOF 4
I'm not trying to be a dick, but if you knew about the bug for that long, Jim would've fixed it for the initial release of FOF2004 if you'd mentioned it to him.
Yossarian
11-25-2003, 03:36 AM
You know...
thats actually a fair point.
The community here is so active, and I'm much more of a lurker - I assumed it was known. In the last version, a patch stated something like "improved reliabilty of play calling screen" or words to that affect. I assumed the patch hadn't 'took' on my system - it wasn't till getting the new game that I realised it wasn't fixed.
I emailed Jim
His reponse:
Thanks for the report. It's a shame that no one reported this in FOF4, or in
FOF 2004 pre-patch. It's hard fixing a long-standing bug if you don't know
about it. I'll take a look at this for the next patch.
-Jim
I guess next time i won't keep shtum.
cthomer5000
11-25-2003, 08:40 AM
Originally posted by Yossarian
I guess next time i won't keep shtum.
everyone can make a difference!
this PSA was brought to you by FOFC.
Solecismic
11-29-2003, 06:32 PM
I've been following up with Yossarian, but his gaming computer is out for repairs. I wondered if anyone who has seen this crash could answer the following questions:
1) Have you ever seen this bug in any other case than when a running back was selected to replace an injured wide receiver in the in-game depth chart?
2) Could someone who has experienced this post the address the game gives you when it crashes (something along the lines of 004a7b35)?
3) Does this happen on any operating system other than XP?
thanks
jetpunk2000
11-29-2003, 08:25 PM
1) Have you ever seen this bug in any other case than when a running back was selected to replace an injured wide receiver in the in-game depth chart?
Does it have to be an injured WR? I just tried replacing a WR with a RB and was able to click view on any play i wanted. I'm running on XP.
AZSpeechCoach
11-29-2003, 08:31 PM
Yossarian? What the hell kind of name is Yossarian?
Couldn't resist.
I think the Yossarians were the Lima Bean cult on the Simpsons.
Na-na-Na-na-Na-na-Na-na-Leader!
AZSpeechCoach
11-30-2003, 05:41 PM
No no...the correct answer is "It's Yossarian's name, sir!"
Anybody get the reference? Anybody?
Easy Mac
11-30-2003, 06:00 PM
I'm assuming Catch-22, but thats too obvious
Yossarian
11-30-2003, 06:18 PM
C22 is where I stole it from.
Its a good name when playing online FPS's - its a soldiers name and sounds.. right.
corbes
11-30-2003, 07:01 PM
Originally posted by Solecismic
I've been following up with Yossarian, but his gaming computer is out for repairs. I wondered if anyone who has seen this crash could answer the following questions:
1) Have you ever seen this bug in any other case than when a running back was selected to replace an injured wide receiver in the in-game depth chart?
2) Could someone who has experienced this post the address the game gives you when it crashes (something along the lines of 004a7b35)?
3) Does this happen on any operating system other than XP?
thanks
I've definitely had this crash on Windows 98. I assumed it was tied into the way that clicking on "play view" brought up the names of players from the wrong team. But it very easily could have been a player out of position -- especially because it surely happened at least once in the 5 WR Spread formation, which I use most often (where a RB fills the 5th WR position). (Incidentally, side note, why can't my 5th WR be my third-string SE? If I choose "Any Wide Receiver", it always picks my starting TE. Granted, the TE is much better than the receiver, but I wanted to get some fresh legs out there).
My gaming computer isn't connected to the internet. But I'll go back and try to replicate that error, and see what the message/number is.
vBulletin v3.6.0, Copyright ©2000-2026, Jelsoft Enterprises Ltd.