Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:

shortcuts: hit alt+s to submit/post or alt+p to preview

Please read the rules before you post!


Topic Summary

Posted by: Jorgen_CAB
« on: July 04, 2020, 12:13:23 PM »

Quote from: SpikeTheHobbitMage on June 11, 2020, 01:35:44 PM
Quote from: Jorgen_CAB on June 07, 2020, 08:58:41 AM
Quote from: Kaiser on June 07, 2020, 07:54:23 AM
The problem here guys, is that entering in a new system you never know if it is populated with some hostile aliens or not.

Let's say my battle fleet just entered a new system, my active sensor did not spot anything (for whatever reason) everything looks quite, then you give order to go to this nice planet 3 billions far from your JP with a 5 days increment, suddently all your ships are destroyed by incoming missles that your point defence did not recognize because the 5 days increment.

If you had used a 8h increment or less you would avoid this, but you could not know it.

That is not hugely likely to happen as the NPR will likely set the pulses to allot lower long before that so you should get a fair warning when something is about to happen.
NPRs do not set pulse times.  Aurora is supposed to override your player selected pulse time while fire controls are active and/or missiles are in flight but it isn't reliable.

But that is the same thing... the game change pulses based on what the NPR does not just what the player does...
Posted by: Kaiser
« on: July 04, 2020, 05:24:41 AM »

Anyway, I think this is the problem, a glitch from the VB6 has been inherited in C version.

I was reading te ship combat page on the Wiki and I found this:

Quote
Warning: there is a glitch in the game that can prevent incoming missiles from being detected and fired upon by your automated defenses if you choose a long increment time in battle. It's safer to stick to increments of under a minute.

Posted by: SpikeTheHobbitMage
« on: June 11, 2020, 01:35:44 PM »

Quote from: Jorgen_CAB on June 07, 2020, 08:58:41 AM
Quote from: Kaiser on June 07, 2020, 07:54:23 AM
The problem here guys, is that entering in a new system you never know if it is populated with some hostile aliens or not.

Let's say my battle fleet just entered a new system, my active sensor did not spot anything (for whatever reason) everything looks quite, then you give order to go to this nice planet 3 billions far from your JP with a 5 days increment, suddently all your ships are destroyed by incoming missles that your point defence did not recognize because the 5 days increment.

If you had used a 8h increment or less you would avoid this, but you could not know it.

That is not hugely likely to happen as the NPR will likely set the pulses to allot lower long before that so you should get a fair warning when something is about to happen.
NPRs do not set pulse times.  Aurora is supposed to override your player selected pulse time while fire controls are active and/or missiles are in flight but it isn't reliable.
Posted by: davidb86
« on: June 11, 2020, 12:55:02 PM »

Quote
I can't remember off the top of my head where to do that in C#, but I do know you can tell them to "Turn Active Sensors On" in the window where you give fleet orders. I believe you can also turn them on manually from the same window where you assign Fire Controls, but I can't quite recall.

In the Naval Organization Window, select the ship (not the fleet) and the active on /active off button is at the bottom of the window
Posted by: Ulzgoroth
« on: June 11, 2020, 04:56:47 AM »

Quote from: xenoscepter on June 11, 2020, 04:46:00 AM
Yeah, just in case you don't know you need Active Sensors to see enemy missiles.

They need to be Resolution 1, and you need to make sure they are turned on. I can't remember off the top of my head where to do that in C#, but I do know you can tell them to "Turn Active Sensors On" in the window where you give fleet orders. I believe you can also turn them on manually from the same window where you assign Fire Controls, but I can't quite recall.
Practically speaking, that's pretty accurate. Strictly speaking, I'm pretty sure it's possible to detect missiles with passive sensors (but not shoot them, that always requires active detection) and to detect missiles with a larger-than-resolution-1 sensor (but the detection range plummets as you crank up the resolution and it's usually shorter than you want at best, so you really want that resolution 1 sensor.)
Posted by: xenoscepter
« on: June 11, 2020, 04:46:00 AM »

Yeah, just in case you don't know you need Active Sensors to see enemy missiles.

They need to be Resolution 1, and you need to make sure they are turned on. I can't remember off the top of my head where to do that in C#, but I do know you can tell them to "Turn Active Sensors On" in the window where you give fleet orders. I believe you can also turn them on manually from the same window where you assign Fire Controls, but I can't quite recall.
Posted by: Ulzgoroth
« on: June 11, 2020, 04:31:30 AM »

Quote from: Peter Rhodan on June 11, 2020, 04:11:06 AM
Okay - my problem is that I don't see the enemy missiles at all - on screen or on my combat screen
Possibly stupid question, but...what actual sensors do you have that you're expecting to spot them with?
Posted by: Peter Rhodan
« on: June 11, 2020, 04:11:06 AM »

Okay - my problem is that I don't see the enemy missiles at all - on screen or on my combat screen
Posted by: Jorgen_CAB
« on: June 07, 2020, 08:58:41 AM »

Quote from: Kaiser on June 07, 2020, 07:54:23 AM
The problem here guys, is that entering in a new system you never know if it is populated with some hostile aliens or not.

Let's say my battle fleet just entered a new system, my active sensor did not spot anything (for whatever reason) everything looks quite, then you give order to go to this nice planet 3 billions far from your JP with a 5 days increment, suddently all your ships are destroyed by incoming missles that your point defence did not recognize because the 5 days increment.

If you had used a 8h increment or less you would avoid this, but you could not know it.

That is not hugely likely to happen as the NPR will likely set the pulses to allot lower long before that so you should get a fair warning when something is about to happen.
Posted by: Kaiser
« on: June 07, 2020, 07:54:23 AM »

The problem here guys, is that entering in a new system you never know if it is populated with some hostile aliens or not.

Let's say my battle fleet just entered a new system, my active sensor did not spot anything (for whatever reason) everything looks quite, then you give order to go to this nice planet 3 billions far from your JP with a 5 days increment, suddently all your ships are destroyed by incoming missles that your point defence did not recognize because the 5 days increment.

If you had used a 8h increment or less you would avoid this, but you could not know it.
Posted by: Jorgen_CAB
« on: June 07, 2020, 06:29:37 AM »

To be honest I don't understand why there is a separate turn button so the game would show what the main and sub cycles are but highlighting them before you hit end turn. If you select 5 day cycles then the game would grey out the sub pulse option that is not possible. This would make it easier to understand for people in general.
Posted by: Bughunter
« on: June 07, 2020, 02:10:19 AM »

Yes, I have also seen this happen in C#.
Posted by: Father Tim
« on: June 06, 2020, 04:35:03 AM »

"If your chosen settings would result in more than 100 sub-pulses, Aurora will ignore your settings and use its defaults."  --  Steve

If you click "5 days" with 1 hour or shorter sub-pulses, Aurora will use 8 hours and your ships will die.
Posted by: Polestar
« on: May 24, 2020, 08:00:11 AM »

Confirmed: The game does not behave the same if you choose 1 day+ increments than if you choose 8 hour- increments. In the former case, sub-increment number is drastically reduced, sensing and opportunities to react happen only on rare occasions, and the game runs faster. In the latter case, sub-increment are respected, sensing and other combat-relevant events happen more often, and the game runs (quite a bit) slower.

I'm giving serious consideration to using the text above as my post tag because this feature trips up *every new player to the game, and quite a few veterans*.

This feature has not changed in essence in the transition to C# Aurora, and continues to be a critical part of Steve's toolkit for delivering an acceptably responsive game.

That said, I do have some major issues with how the game continues to fall down on managing automatic transitions between the two and consider them among the most vexing, systemic problems with the Aurora game engine. Forgive my heat, fellow players, but losing entire fleets to the game effectively turning off my sensors when I hit a button right next to the save game button ... is worth getting a tad perturbed about.



Posted by: QuakeIV
« on: May 23, 2020, 05:01:56 PM »

In the past, pretty careful micromanagement of the time increments has been necessary or you will die.  I haven't had much combat yet in the new version to check that out (i had like a week long game where i found no aliens).