The International Simutrans Forum

Simutrans Extended => Pak128.Britain-Ex Bug Reports => Pak128.Britain-Ex => Simutrans-Extended paksets => Pak128.Britain-Ex closed bug reports => Topic started by: ӔO on December 30, 2011, 09:17:14 PM

Title: [0.8.3] PS Comet steam ship maint. costs too much
Post by: ӔO on December 30, 2011, 09:17:14 PM
at a cost of 20.48c (10.24 x2) it just costs way too much to be profitable.

The east indiaman that can haul 100 pax for 4.50c can barely break even with pax only.
Perhaps the maint. for the PS comet can be lowered to 5.12c total?
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: jamespetts on December 30, 2011, 09:31:17 PM
AEO,

thank you very much for the observation: this is most helpful. May I ask, for the purposes of calculating these things in future, how you came to work out that the maintenance was excessive?
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: ӔO on December 30, 2011, 10:12:56 PM
@james
in my network, each PS comet ship is losing something like 700~800c each month even with the pax portion full.
All the horse and carriage lines are at 110~200% capacity and it's still impossible to run long distance ships, because they cost too much. Short distances to close gaps in the network are okay, but they are still at a loss.

At one point, I tried running a long distance east indiaman pax only service, but that caused something along the lines of -500,000c total yearly profits.
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: jamespetts on December 30, 2011, 10:15:27 PM
Hmm. I did think that I had achieved an approximate balance of these by calculating the cost as a factor of the cost of the number of railway locomotives of the period necessary to haul enough carriages to carry an equivalent number of passengers. Perhaps I have miscalculated. I shall have to look into reducing the costs as you suggest when I have a moment.
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: ӔO on December 30, 2011, 11:33:38 PM
here is a save file:
lines 10, 24 and 25 are bleeding money
http://dl.dropbox.com/u/17111233/Turnkey%201817.sve
(http://dl.dropbox.com/u/17111233/Turnkey%201817.sve)
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: jamespetts on December 31, 2011, 09:34:03 PM
I have pushed some changes (mainly a reduction by about 40% in many ship costs, and of less in some other ship costs) to my Github repository. Are you able to compile the pakset and test the modified values?  Thank you very much for reporting this.

Edit: Trying your saved game on my Linux binary build, I get a segfault almost immediately on loading. Are you using the latest 10.4 Experimental binaries for this? If so, what platform are you using, may I ask?
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: ӔO on January 01, 2012, 12:13:11 AM
it's the 10.4, ipv4 version with matching config and it was saved under winXP.
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: jamespetts on January 01, 2012, 12:47:22 AM
Hmm, interesting. I haven't had any reports of Linux specific crashes. It might be my graphics drivers, as I am on a very old machine with a somewhat ancient graphics card that doesn't work as well as it should, and performance moving around the map is very poor, but I still wonder that there might be a bug.

In any event - do let me know whether/when you have managed to test the new ship costs.
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: ӔO on January 01, 2012, 04:16:37 AM
it could be the sheer number of convoys, as I am barely getting 8~9x on fast forward in the game with a 1.83ghz core 2 duo.

there are something like 2400+ convoys on that map.
Title: Re: [0.8.3] PS Comet steam ship maint. costs too much
Post by: jamespetts on January 01, 2012, 11:29:37 AM
That wouldn't cause a segmentation fault: a segmentation fault is when a program tries to read or write to memory at an address not allotted to that program, for example, if the program tries to use a null pointer or a memory address that has been deleted.