Author Topic: Suggestions for 3.3  (Read 12452 times)

0 Members and 1 Guest are viewing this topic.

Offline jfelten

  • Lieutenant
  • *******
  • j
  • Posts: 187
Re: Suggestions for 3.3
« Reply #150 on: March 11, 2009, 01:41:38 PM »
Quote from: "waresky"
ive narrow to 2500Officers..and have Ages before am check every damned officers..
And coming some bugs,in Team options...:S srry for Out of topic.But hope steve take some "lite" operation to better performance on Officer "bar"_:)

Geesh.  25K Officers.  I don't know what Steve is doing in his code but perhaps adding a primary key somewhere would speed things up dramatically.
 

Offline Kurt (OP)

  • Gold Supporter
  • Vice Admiral
  • *****
  • Posts: 1766
  • Thanked: 3389 times
  • 2021 Supporter 2021 Supporter : Donate for 2021
    Gold Supporter Gold Supporter : Support the forums with a Gold subscription
    2022 Supporter 2022 Supporter : Donate for 2022
    2023 Supporter 2023 Supporter : Donate for 2023
Re: Suggestions for 3.3
« Reply #151 on: March 28, 2009, 01:44:49 PM »
Steve -

I know you just released 4.0b, but after plotting out a major colonial effort for a system four jumps away from Earth, I had an idea.  I have no idea if it would be hard or easy to program, but it sure would make things easier when giving orders.  Would it be possible, when giving movement commands on the task group screen, to change things so that instead of having to give orders like this: "Move to warp point A, transit warp point A, move to warp point B, transit warp point B, move to warp point C, transit warp point C, move to planet D", I could could instead select a destination from a list of my race's populations, and then Aurora would calculate the path from System A to System C, planet D?  I know it might be problematic if there are multiple paths, and pathfinding might be problematic even if there is only one, but giving these movement orders is time consuming, and if it could be streamlined it would help reduce the overhead greatly.

Thanks -

Kurt
 

Offline SteveAlt

  • Global Moderator
  • Rear Admiral
  • *****
  • Posts: 820
  • Thanked: 8 times
Re: Suggestions for 3.3
« Reply #152 on: March 28, 2009, 01:54:15 PM »
Quote from: "jfelten"
Quote from: "waresky"
ive narrow to 2500Officers..and have Ages before am check every damned officers..
And coming some bugs,in Team options...:S srry for Out of topic.But hope steve take some "lite" operation to better performance on Officer "bar"_:)

Geesh.  25K Officers.  I don't know what Steve is doing in his code but perhaps adding a primary key somewhere would speed things up dramatically.
I have been database programming for 20 years so there are one or two primary keys scattered about. A few foreign ones as well.

Steve
 

Offline SteveAlt

  • Global Moderator
  • Rear Admiral
  • *****
  • Posts: 820
  • Thanked: 8 times
Re: Suggestions for 3.3
« Reply #153 on: March 28, 2009, 01:57:49 PM »
Quote from: "Kurt"
Steve -

I know you just released 4.0b, but after plotting out a major colonial effort for a system four jumps away from Earth, I had an idea.  I have no idea if it would be hard or easy to program, but it sure would make things easier when giving orders.  Would it be possible, when giving movement commands on the task group screen, to change things so that instead of having to give orders like this: "Move to warp point A, transit warp point A, move to warp point B, transit warp point B, move to warp point C, transit warp point C, move to planet D", I could could instead select a destination from a list of my race's populations, and then Aurora would calculate the path from System A to System C, planet D?  I know it might be problematic if there are multiple paths, and pathfinding might be problematic even if there is only one, but giving these movement orders is time consuming, and if it could be streamlined it would help reduce the overhead greatly.
It is possible, although tricky over longer distances. The civilian and NPR code has to work out the route to various destinations so that could be adapted. It currently has a 4 system max limit though. I agree it would be useful though so I'll add it to my list of important mods.

Steve
 

Offline SteveAlt

  • Global Moderator
  • Rear Admiral
  • *****
  • Posts: 820
  • Thanked: 8 times
Re: Suggestions for 3.3
« Reply #154 on: March 28, 2009, 05:21:21 PM »
Quote from: "SteveAlt"
Quote from: "Kurt"
Steve -

I know you just released 4.0b, but after plotting out a major colonial effort for a system four jumps away from Earth, I had an idea.  I have no idea if it would be hard or easy to program, but it sure would make things easier when giving orders.  Would it be possible, when giving movement commands on the task group screen, to change things so that instead of having to give orders like this: "Move to warp point A, transit warp point A, move to warp point B, transit warp point B, move to warp point C, transit warp point C, move to planet D", I could could instead select a destination from a list of my race's populations, and then Aurora would calculate the path from System A to System C, planet D?  I know it might be problematic if there are multiple paths, and pathfinding might be problematic even if there is only one, but giving these movement orders is time consuming, and if it could be streamlined it would help reduce the overhead greatly.
It is possible, although tricky over longer distances. The civilian and NPR code has to work out the route to various destinations so that could be adapted. It currently has a 4 system max limit though. I agree it would be useful though so I'll add it to my list of important mods.
This proved easier than I expected. There is now a new System Location Display Option for All Pops on the Fleet window. When this is selected you can see all populations in the list of destinations. As you select one you get the usual list of move options such as Resupply from Colony, Move to, etc. Except in this case it fills in the intervening transits automatically. This will only work for colonies within four jumps that can be reached by the fleet in question. The code is aware of jump gates and jump engines when it works this out. If it can't work out a route or you select a colony further away than four jumps, you will get a popup stating that no route can be found. If you are 5 jumps away just plot the first transit and then use the auto-route for the rest of the trip. When I get chance I will upgrade the route finding code to handle more than 4 jumps.

I could try and restrict the list to only those pops you can reach but that would involve working out the route to every colony before the list is displayed and that would take a while.

Steve