Posted by: TT
« on: September 08, 2015, 08:45:57 AM »Quote
Sounds like Steve fixed this for 6.5
Great! looking forward to 6.5
Great! looking forward to 6.5
Posted by: SteelChicken
« on: September 08, 2015, 08:36:25 AM »I logged in to the forum to recommend this very thing after doing about an hour and a half at 15 second increments with "GetMaxPotentialSensorRange" errors (error number 6) four times in each turn resolution. This appears to be NPRs fighting it out and the error messages keep you from auto turning your way out of the NPR skirmish. So let me add my vote to HavingPhun's fine suggestion.
Sounds like Steve fixed this for 6.5
Posted by: TT
« on: September 08, 2015, 07:57:49 AM »I logged in to the forum to recommend this very thing after doing about an hour and a half at 15 second increments with "GetMaxPotentialSensorRange" errors (error number 6) four times in each turn resolution. This appears to be NPRs fighting it out and the error messages keep you from auto turning your way out of the NPR skirmish. So let me add my vote to HavingPhun's fine suggestion.
Posted by: HavingPhun
« on: September 01, 2015, 09:32:27 PM »Quote from: Steve Walmsley link=topic=7893. msg80645#msg80645 date=1441114387
There are a couple of issues with this proposal.
1) There are some errors you can easily fix (and in fact have to fix or the game will continue to have short increments giving you the same error every time), or have known workarounds. There is no way for the game to know which errors you can easily fix and therefore only show those
2) Some errors, especially data access ones, result in an endless series of error 91s (Microsoft error codes). With no popups, the game will simply hang for no apparent reason.
Obviously the ideal is to have no popup errors. My current campaign has had only one so far, connected with the Check All Pops option, which is now fixed If you do have errors though, read the message and report them so I can fix them for the next version.
Ah well, I had hoped the second bit wasn't the case. Thanks for the reply.
Posted by: SteelChicken
« on: September 01, 2015, 03:23:42 PM »Posted by: Steve Walmsley
« on: September 01, 2015, 03:17:11 PM »Yes, NPR ships with massive active sensors cause an error. I don't have the detailed error message (I can get the detailed error later on tonight) but here is a comment from the 6.4 bug thread I made.
"I found some NPR ships with the following sensors:
Active Search Sensor MR1737-R97
Active Search Sensor MR2481-R97
When I deleted them the errors stopped."
This particular error fires quite frequently...one pop up per ship per increment.
I've fixed this for v6.50
Posted by: TheDeadlyShoe
« on: September 01, 2015, 02:54:15 PM »yeah npr sensors can be weird.
in my intelligence screen i noticed a 200kt swarm mothership that had a str 0.00000000023928398 or somewhere therabouts strength sensor on it (as well as the one that works)
in my intelligence screen i noticed a 200kt swarm mothership that had a str 0.00000000023928398 or somewhere therabouts strength sensor on it (as well as the one that works)
Posted by: SteelChicken
« on: September 01, 2015, 09:06:21 AM »Remind me of the max sensor range error
Yes, NPR ships with massive active sensors cause an error. I don't have the detailed error message (I can get the detailed error later on tonight) but here is a comment from the 6.4 bug thread I made.
"I found some NPR ships with the following sensors:
Active Search Sensor MR1737-R97
Active Search Sensor MR2481-R97
When I deleted them the errors stopped."
This particular error fires quite frequently...one pop up per ship per increment.
Posted by: Steve Walmsley
« on: September 01, 2015, 08:45:26 AM »Remind me of the max sensor range error Some type of overflow?
Some type of overflow?Posted by: SteelChicken
« on: September 01, 2015, 08:41:05 AM »There are a couple of issues with this proposal.
1) There are some errors you can easily fix (and in fact have to fix or the game will continue to have short increments giving you the same error every time), or have known workarounds. There is no way for the game to know which errors you can easily fix and therefore only show those
2) Some errors, especially data access ones, result in an endless series of error 91s (Microsoft error codes). With no popups, the game will simply hang for no apparent reason.
Obviously the ideal is to have no popup errors. My current campaign has had only one so far, connected with the Check All Pops option, which is now fixed If you do have errors though, read the message and report them so I can fix them for the next version.
Understood...Steve, have you made any changes to the way the NPR's design active sensors to avoid the maxsensorrange bug?
Posted by: Steve Walmsley
« on: September 01, 2015, 08:33:07 AM »There are a couple of issues with this proposal.
1) There are some errors you can easily fix (and in fact have to fix or the game will continue to have short increments giving you the same error every time), or have known workarounds. There is no way for the game to know which errors you can easily fix and therefore only show those
2) Some errors, especially data access ones, result in an endless series of error 91s (Microsoft error codes). With no popups, the game will simply hang for no apparent reason.
Obviously the ideal is to have no popup errors. My current campaign has had only one so far, connected with the Check All Pops option, which is now fixed If you do have errors though, read the message and report them so I can fix them for the next version.
1) There are some errors you can easily fix (and in fact have to fix or the game will continue to have short increments giving you the same error every time), or have known workarounds. There is no way for the game to know which errors you can easily fix and therefore only show those
2) Some errors, especially data access ones, result in an endless series of error 91s (Microsoft error codes). With no popups, the game will simply hang for no apparent reason.
Obviously the ideal is to have no popup errors. My current campaign has had only one so far, connected with the Check All Pops option, which is now fixed If you do have errors though, read the message and report them so I can fix them for the next version.
Posted by: SteelChicken
« on: September 01, 2015, 08:18:24 AM »Yes. This is usually why I abandon games. My current game has been ALOT of fun, but I am swamped with 6-10 error popups each turn.
Posted by: xeryon
« on: September 01, 2015, 07:56:52 AM »I know. It would be nice though. Sometimes the error windows indicate something that a player can resolve, like a travel order that will take so many years it exceeds the travel time field. i.e. a ship moving at 1kms that was told to travel 10 jumps away or something. Otherwise, the errors are often something you can't do anything about but you don't want to give up on the game. If it will keep going why not? If it generates 10 error windows every increment and clicking ten times on the okay button is driving you nuts and you just want to see if your ships can take out the Queen...
Posted by: MarcAFK
« on: September 01, 2015, 07:40:48 AM »Of course it's likely the popular error windows are a Visual Basic thing that might not be easy to suppress.
Posted by: xeryon
« on: September 01, 2015, 07:32:47 AM »Simple then: checkmark option to have all popup error windows dump data to a temp log file instead of error windows. Game will keep running until it doesn't regardless of the errors. Use at your own peril.
