1.06 Subproject: Prevent AIs from reusing logos
1.06 Subproject: Prevent AIs from reusing logos
Quick question on this one: should random AI companies be able to pick custom logos, or should those be reserved for player companies and for premade AIs?
Sorry - I'm not tackling any of the AI complaints before I've funneled the function calls into Python, which means 1.07 at the earliest. Creating AIs is bloody difficult even when I'm not trying to reverse-engineer some junior hacker's Microsoft-compiled C++ without the source code.
Bit stressed. The beta's gotta go out next weekend if we want to hit a late-Feb release date, I'm only halfway through the patch list, and neither Bombardiere's team nor most of the testers are reporting in. Dropped the track build radius fix and the rail graphics fixes - couldn't figure out how to do them. Good news is that my new company let me take a month to recuperate from my old one, so I have a bit more time to work on this.
Bit stressed. The beta's gotta go out next weekend if we want to hit a late-Feb release date, I'm only halfway through the patch list, and neither Bombardiere's team nor most of the testers are reporting in. Dropped the track build radius fix and the rail graphics fixes - couldn't figure out how to do them. Good news is that my new company let me take a month to recuperate from my old one, so I have a bit more time to work on this.
I agree with Hawk, don't stress! I'm sure Bombardiere is very busy working on the locos, hence his long absences from the forum. I'm currently incapacitated (computer dead), although new cargos are no longer on the cards for the patch.
More on topic- I've actually written a few AIs, in a script quite similar to Java. I must have spent a total of 100+ hours figuring out how it all worked, but that was a while ago, and RT3's AI script is probably very different.
Anyway, do what you can, and don’t stress.
More on topic- I've actually written a few AIs, in a script quite similar to Java. I must have spent a total of 100+ hours figuring out how it all worked, but that was a while ago, and RT3's AI script is probably very different.
Anyway, do what you can, and don’t stress.
<ghastly grin> You want to know about RT3's AI 'script?' Take a look at the machine language from 404CE0-405913. That's how (I think) the AI decides which two towns to connect. Not where to lay the track, just which two towns to connect. Oh, you may want to have the Bufferin handy...
Thanks for the advice on not stressing, guys, but after Feb my regular schedule goes back to nasty. And you're right about the semi-functioning stuff; that's why the testers need three weeks to play with it, and why I've been putting out early-access alphas of the pieces most likely to have side-effects.
Thanks for the advice on not stressing, guys, but after Feb my regular schedule goes back to nasty. And you're right about the semi-functioning stuff; that's why the testers need three weeks to play with it, and why I've been putting out early-access alphas of the pieces most likely to have side-effects.
-
bombardiere
- Dispatcher
- Posts: 425
- Joined: Tue Nov 14, 2006 9:07 am
- Location: Turku, Finland
Busy yes, but not with locos. :( Well actually I have implemented most of the changes I want to and I try to gather everything in next couple days. As I am not able to access FTP (no own internet connection), I think that I will send files to Hawk and he can post those.I agree with Hawk, don't stress! I'm sure Bombardiere is very busy working on the locos, hence his long absences from the forum.
Milo don't worry about the schedule. It is your project and as you do the work, set our own timetable. P.S. I guess you didn't receive my PM. Most of it is unimportant now, but could you please send me the Loco pack's pre-PDF documentation to me. I want to make some improvements, mainly at the pictures.
Oh, gosh. I did receive your PM, Bombardiere, and promptly forgot it. Belated E-mail on the way with a 5MB attachment.
And it's OUR project. The testers and the artists' parts aren't any less important than the coder's part. Without you, we don't get shiny new locos, which are the most popular part of these releases (check Hawk's download stats if you don't believe me!). Without the testers, it's too dangerous to release the patch. Without the interpreters, we'll lose the input from Molse and his forum again... Everyone here plays important parts; mine just happen to be upstream from yours and are going the slowest.
And it's OUR project. The testers and the artists' parts aren't any less important than the coder's part. Without you, we don't get shiny new locos, which are the most popular part of these releases (check Hawk's download stats if you don't believe me!). Without the testers, it's too dangerous to release the patch. Without the interpreters, we'll lose the input from Molse and his forum again... Everyone here plays important parts; mine just happen to be upstream from yours and are going the slowest.
Well... already figured out the beta was going to slip... and ten minutes ago my PC abruptly turned itself off without warning, which probably means its temp controller is on the fritz again. Guess Murphy agrees with you guys on the schedule. 
New Beta release target is Friday 2007/02/16 if I still have a working PC.
New Beta release target is Friday 2007/02/16 if I still have a working PC.