I'm having the same issue. The game closes and a pop-up window appears stating: Runtime error... R6025.. pure virtual function call.
Has happened twice to me so far, in the second game after every start up. Occurs when simply pressing space bar to bowl overs during a game.
(Sorry, posted this in the Bugs/Crashes forum thread too).
Announcement
Collapse
No announcement yet.
bug - pure virtual function call
Collapse
X
-
Originally posted by Chris Child View PostIf not using space bar, were you using auto-play?
Did it say 'pure virtual' in the error?
Leave a comment:
-
Originally posted by Chris Child View PostThanks, I'm just checking to see our fix would still apply. The fact it doesn't happen too often to you means we're probably on the right track.
Leave a comment:
-
Thanks, I'm just checking to see our fix would still apply. The fact it doesn't happen too often to you means we're probably on the right track.
Leave a comment:
-
Originally posted by Chris Child View PostIf not using space bar, were you using auto-play?
Did it say 'pure virtual' in the error?
Yes it did
I play one over at a time, with either low highlights when bowling , or high when batting - not sure if relevant.
If a highlight appears then I will click to bring it to an end maybe a second before it finishes naturally - again not sure of relevant
Plus I tend to tinker with field placing each over
Leave a comment:
-
If not using space bar, were you using auto-play?
Did it say 'pure virtual' in the error?
Leave a comment:
-
Just had this error for the first time - half way through a game
No use of the space bar
Leave a comment:
-
Can you tell us if you play the match using "space bar". I've found an issue with that that might be causing the problem.
Leave a comment:
-
Originally posted by Chris Child View PostIf you can grab a screen-shot of the whole screen when it crashes, that would be very helpful. We've has a few reports of it happening just after an interval when you click "match analysis". I think others have had the issue in different places though, and a screen-shot will help us identify the match state.
If you know anything about the match state when it happens, let us know:
- just after an interval/just after a change of innings/middle of a session?
- clicking play over or something else? What had you just done?
- match type and how far through the match (4th innings seems to be common)
Leave a comment:
-
Happened to me as well, the details I can give was, I was playing as Lancashire and the opposition was 9 down and 9 and 11 were batting, in the last game of the season and I had two quick bowlers bowling around the wicket short stuff on full aggression when it crashed.
Leave a comment:
-
Just got this error again, this time just as I went to start the match!
Leave a comment:
-
If you can grab a screen-shot of the whole screen when it crashes, that would be very helpful. We've has a few reports of it happening just after an interval when you click "match analysis". I think others have had the issue in different places though, and a screen-shot will help us identify the match state.
If you know anything about the match state when it happens, let us know:
- just after an interval/just after a change of innings/middle of a session?
- clicking play over or something else? What had you just done?
- match type and how far through the match (4th innings seems to be common)
Leave a comment:
-
This has happened with less frequency of late - I save compulsively to try and get around it, but happened again today. The one thing I can say is it always happens within a match, though not during a highlight.
I'll keep an eye on this thread and hopefully it will soon be solved.
Leave a comment:
Leave a comment: