Posted by: Darknote
« on: June 28, 2020, 04:32:29 PM »@Thrake, I'm curious, how long do 1 day turns take in a game with 10 NPR's?
Posted by: mike2R
« on: June 19, 2020, 08:58:55 AM »Sweet! Glad you got to the bottom of it!
Posted by: Thrake
« on: June 19, 2020, 08:32:44 AM »Very frustrating yes, this is a long game. There are a lot of NPR, I have found 10 until now so the galaxy is well populated.
Thanks a lot for your feedback mike2R! Following your tip, my first thing was to check a system I knew had many wrecks and populated with what I think is a spoiler. Adding tracking stations I found there was a big NPR fleet immobile there. So, I SMed in a doomship, killed the spoiler ships, the NPR fleet started moving afterwards. Quickly after there was a battle in the system (I had put my tracking station at the same colony than the spoiler so its ground forces destroyed them, I'm not sure what exactly happened) and now everything is back to normal.
At that point I was really thinking of giving up with the game.
Thanks a lot for your feedback mike2R! Following your tip, my first thing was to check a system I knew had many wrecks and populated with what I think is a spoiler. Adding tracking stations I found there was a big NPR fleet immobile there. So, I SMed in a doomship, killed the spoiler ships, the NPR fleet started moving afterwards. Quickly after there was a battle in the system (I had put my tracking station at the same colony than the spoiler so its ground forces destroyed them, I'm not sure what exactly happened) and now everything is back to normal.
At that point I was really thinking of giving up with the game.
Posted by: Zincat
« on: June 19, 2020, 07:57:02 AM »It's still rather strange if it keeps doing 6 hours increments forever...
Maybe post it in the bug reporting thread, with the db included? I mean, if it NEVER stops, then something is definitely not working as intended.
Maybe post it in the bug reporting thread, with the db included? I mean, if it NEVER stops, then something is definitely not working as intended.
Posted by: mike2R
« on: June 19, 2020, 06:20:57 AM »One thought - you have contact with at least 1 NPR from what you've said. So if you use SM mode instant grav survey and explore jump gates, you might be able to find its own explored systems - unless there is some way to tell, you'd basically be looking for its own gate network to distinguish between ones it's explored, and ones that were being generated new for you. Maybe you can find the problem system that way.
Posted by: mike2R
« on: June 19, 2020, 06:12:24 AM »I've not had it in C#, but in VB6 I've had things like this that were caused by an unarmed or out of ammo AI ship, in a system that I had a presence in.
The AI would move to a point where it was able to detect my ship on its sensors, which caused the interrupt, but didn't give a message because my ship couldn't detect it back.
And once it saw my ship it would move away since it had no way to attack it. Then it would move back towards it again because its dumb. Rinse and repeat.
Tended to happen in systems I'd cleared of Precursors. Using SM mode to dump 10,000 tracking stations on a body is a way to check a system for it.
Interesting.
I dumped tracking stations in every systems I had colonies, found a gravsurvey NPR ship that was not moving. Making him meet his maker did not solve my issue however. It has now been a year at 6 hours increments.
I will try to recall all my survey ships, perhaps there is another NPR ship causing issues somewhere.
Edit: No, the issue has still not been solved.
That's a shame...
Pretty much must be something happening between AIs then, and the 6 hour thing still makes it feel like its to do with detection to me... I don't think combat could be that regular for that length of time.
I think C# still gives you the same sensor game options you got in VB6...? The always detect without player presence, and no detection without player presence ones. Maybe running the game with one of those for a chunk might clear it - push the AI into doing something else, or just blowing each other up and getting it over with.
Detection setting? Good idea. I tried to set it to none without player presence, click save settings, then play game and when I check the settings again it is normal detection mode again.
God how frustrating...! Apart from trying manual database edits, I can't think of anything else - you've eliminated systems you have any vision over being the cause of the problem, so i don't know of any other way you can effect whatever is causing the issue.
Posted by: Thrake
« on: June 19, 2020, 06:04:13 AM »I've not had it in C#, but in VB6 I've had things like this that were caused by an unarmed or out of ammo AI ship, in a system that I had a presence in.
The AI would move to a point where it was able to detect my ship on its sensors, which caused the interrupt, but didn't give a message because my ship couldn't detect it back.
And once it saw my ship it would move away since it had no way to attack it. Then it would move back towards it again because its dumb. Rinse and repeat.
Tended to happen in systems I'd cleared of Precursors. Using SM mode to dump 10,000 tracking stations on a body is a way to check a system for it.
Interesting.
I dumped tracking stations in every systems I had colonies, found a gravsurvey NPR ship that was not moving. Making him meet his maker did not solve my issue however. It has now been a year at 6 hours increments.
I will try to recall all my survey ships, perhaps there is another NPR ship causing issues somewhere.
Edit: No, the issue has still not been solved.
That's a shame...
Pretty much must be something happening between AIs then, and the 6 hour thing still makes it feel like its to do with detection to me... I don't think combat could be that regular for that length of time.
I think C# still gives you the same sensor game options you got in VB6...? The always detect without player presence, and no detection without player presence ones. Maybe running the game with one of those for a chunk might clear it - push the AI into doing something else, or just blowing each other up and getting it over with.
Detection setting? Good idea. I tried to set it to none without player presence, click save settings, then play game and when I check the settings again it is normal detection mode again.
Posted by: mike2R
« on: June 19, 2020, 05:51:47 AM »I've not had it in C#, but in VB6 I've had things like this that were caused by an unarmed or out of ammo AI ship, in a system that I had a presence in.
The AI would move to a point where it was able to detect my ship on its sensors, which caused the interrupt, but didn't give a message because my ship couldn't detect it back.
And once it saw my ship it would move away since it had no way to attack it. Then it would move back towards it again because its dumb. Rinse and repeat.
Tended to happen in systems I'd cleared of Precursors. Using SM mode to dump 10,000 tracking stations on a body is a way to check a system for it.
Interesting.
I dumped tracking stations in every systems I had colonies, found a gravsurvey NPR ship that was not moving. Making him meet his maker did not solve my issue however. It has now been a year at 6 hours increments.
I will try to recall all my survey ships, perhaps there is another NPR ship causing issues somewhere.
Edit: No, the issue has still not been solved.
That's a shame...
Pretty much must be something happening between AIs then, and the 6 hour thing still makes it feel like its to do with detection to me... I don't think combat could be that regular for that length of time.
I think C# still gives you the same sensor game options you got in VB6...? The always detect without player presence, and no detection without player presence ones. Maybe running the game with one of those for a chunk might clear it - push the AI into doing something else, or just blowing each other up and getting it over with.
Posted by: Thrake
« on: June 19, 2020, 05:51:14 AM »I deleted all my pops (other than Earth) and all my fleets but no change. I think it's fair to say that the issue does not come from something happening in my empire or an interaction with an NPR.
Posted by: Thrake
« on: June 19, 2020, 05:06:51 AM »I've not had it in C#, but in VB6 I've had things like this that were caused by an unarmed or out of ammo AI ship, in a system that I had a presence in.
The AI would move to a point where it was able to detect my ship on its sensors, which caused the interrupt, but didn't give a message because my ship couldn't detect it back.
And once it saw my ship it would move away since it had no way to attack it. Then it would move back towards it again because its dumb. Rinse and repeat.
Tended to happen in systems I'd cleared of Precursors. Using SM mode to dump 10,000 tracking stations on a body is a way to check a system for it.
Interesting.
I dumped tracking stations in every systems I had colonies, found a gravsurvey NPR ship that was not moving. Making him meet his maker did not solve my issue however. It has now been a year at 6 hours increments.
I will try to recall all my survey ships, perhaps there is another NPR ship causing issues somewhere.
Edit: No, the issue has still not been solved.
Posted by: mike2R
« on: June 19, 2020, 03:43:13 AM »I've not had it in C#, but in VB6 I've had things like this that were caused by an unarmed or out of ammo AI ship, in a system that I had a presence in.
The AI would move to a point where it was able to detect my ship on its sensors, which caused the interrupt, but didn't give a message because my ship couldn't detect it back.
And once it saw my ship it would move away since it had no way to attack it. Then it would move back towards it again because its dumb. Rinse and repeat.
Tended to happen in systems I'd cleared of Precursors. Using SM mode to dump 10,000 tracking stations on a body is a way to check a system for it.
The AI would move to a point where it was able to detect my ship on its sensors, which caused the interrupt, but didn't give a message because my ship couldn't detect it back.
And once it saw my ship it would move away since it had no way to attack it. Then it would move back towards it again because its dumb. Rinse and repeat.
Tended to happen in systems I'd cleared of Precursors. Using SM mode to dump 10,000 tracking stations on a body is a way to check a system for it.
Posted by: Thrake
« on: June 19, 2020, 01:52:12 AM »It might NPRs fighting with each other, in which case there isn't much you can do.
It might also be your own fire controls looking for targets, so it might be worth checking that all of your unneeded fire controls are off.
In both of these cases he would be stuck in 5 sec increments not 6 hours.
I recommend checking "show all events" on the events tab, you may have hidden some interrupt event that is firing.
6 hour isn't a valid increment in either case? Pretty sure your options are 3 hours or 8 hours.
6 hours isn't an increment you can pick however if you pick an increment size that is greater than 8 and some sort of interrupt fires the game can start to progress the game in 6 hour chunks. For example, if a fleet completes its movement orders in 15.5 days and you pick a 30 day increment the game will progress the 15.5 days. In this example the event "orders complete" adjusts your increment size to 15.5 days. Something similar is probably happening here like a hidden "pickup failed" that keeps progressing the game in 6 hour chunks. Not sure if "pickup failed" is a good example but you get my point.
You've also got "imminent action" interrupts which are related to combat e.g active FCs without targets, enemy weapons discharge that will usually auto-adjust your increment size to 5 secs.
Point is, 6 hour increments are a result of something going on in the player empire, the events log with "show all events" checked will show it pretty well. I find it unlikely that NPR vs. NPR combat would reduce to 6 hours, I would expect 5 seconds.
Good idea, but most of my log entries are empty. This is also what confuse me, I don't understand what is causing this for so long. NPR xenocide happens from time to time but then I just let the computer run for a while.
Posted by: SpikeTheHobbitMage
« on: June 18, 2020, 09:37:01 PM »Hadn't thought of that, but isn't ground combat in 8 hour increments? Either way this is probably whats happeningYou are correct. I'm not sure where I got 6 from. Sorry.
Posted by: Droll
« on: June 18, 2020, 08:54:11 PM »6 hours indicates ground combat in progress.It might NPRs fighting with each other, in which case there isn't much you can do.
It might also be your own fire controls looking for targets, so it might be worth checking that all of your unneeded fire controls are off.
In both of these cases he would be stuck in 5 sec increments not 6 hours.
I recommend checking "show all events" on the events tab, you may have hidden some interrupt event that is firing.
6 hour isn't a valid increment in either case? Pretty sure your options are 3 hours or 8 hours.
6 hours isn't an increment you can pick however if you pick an increment size that is greater than 8 and some sort of interrupt fires the game can start to progress the game in 6 hour chunks. For example, if a fleet completes its movement orders in 15.5 days and you pick a 30 day increment the game will progress the 15.5 days. In this example the event "orders complete" adjusts your increment size to 15.5 days. Something similar is probably happening here like a hidden "pickup failed" that keeps progressing the game in 6 hour chunks. Not sure if "pickup failed" is a good example but you get my point.
You've also got "imminent action" interrupts which are related to combat e.g active FCs without targets, enemy weapons discharge that will usually auto-adjust your increment size to 5 secs.
Point is, 6 hour increments are a result of something going on in the player empire, the events log with "show all events" checked will show it pretty well. I find it unlikely that NPR vs. NPR combat would reduce to 6 hours, I would expect 5 seconds.
Hadn't thought of that, but isn't ground combat in 8 hour increments? Either way this is probably whats happening
Posted by: SpikeTheHobbitMage
« on: June 18, 2020, 08:53:12 PM »6 hours indicates ground combat in progress.It might NPRs fighting with each other, in which case there isn't much you can do.
It might also be your own fire controls looking for targets, so it might be worth checking that all of your unneeded fire controls are off.
In both of these cases he would be stuck in 5 sec increments not 6 hours.
I recommend checking "show all events" on the events tab, you may have hidden some interrupt event that is firing.
6 hour isn't a valid increment in either case? Pretty sure your options are 3 hours or 8 hours.
6 hours isn't an increment you can pick however if you pick an increment size that is greater than 8 and some sort of interrupt fires the game can start to progress the game in 6 hour chunks. For example, if a fleet completes its movement orders in 15.5 days and you pick a 30 day increment the game will progress the 15.5 days. In this example the event "orders complete" adjusts your increment size to 15.5 days. Something similar is probably happening here like a hidden "pickup failed" that keeps progressing the game in 6 hour chunks. Not sure if "pickup failed" is a good example but you get my point.
You've also got "imminent action" interrupts which are related to combat e.g active FCs without targets, enemy weapons discharge that will usually auto-adjust your increment size to 5 secs.
Point is, 6 hour increments are a result of something going on in the player empire, the events log with "show all events" checked will show it pretty well. I find it unlikely that NPR vs. NPR combat would reduce to 6 hours, I would expect 5 seconds.
