I'm going to kick off this thread with some 'SIDE BUSINESS' FROM UPSTREAM IN THIS 'Validation, Validation' THREAD to remain on point. Ive been studying N3V and the Trainz release history, shortcomings, fixups and so forth both for the attempts to userfy the N3V Wiki, but also for updating the Wikibook. Someone has to write some stuff for beginner Trainzers, and N3V has had since 2008 to get something together in the TrainzOnline Wiki. We all know how it hasn't happened. I have about 20% of the edits in the N3V wiki, but Windwalkr wants nothing to reflect the N3V we all experience. This thread starts with that topic, in point, counter-point order, but in a day or three and for a while after that, I'm going to post fixes that the community should consider, and the reason why they are more important than TANE to the survival of N3V and Trainz by any release date.
This continues from a discussion where I excerpted a bunch of emails that pointed out there were quite a few unhappy with the N3V status quo in TS12, most quoted being software savvy like myself:
NOT my comment, as with many in that pistache. Just the way the wind blows from some other software people I network with, not all of them in Yesterdayz Trainz, either. Personally, I figure you've got a bit of PTSD, and should have been relieved of your "FACE" duties here on the forum several years ago. MANY of your answers come off as snippy, juvenile, and dismissive, and as the poster noted above, you run and hide often enough to be twitted about it.
As chief software geek, you have better things to do, I'm sure, and frankly your lack of sensitivity just alienates the people because your impatience shines through. People usually refer to that as arrogance, and believe it or not, I usually defend you on that. Actually, I defend you quite a bit. Mostly I point out that that appellation is not quite accurate, and you have other things you're balancing. As a designer I understand that very well. I'm heartened that you admit here that your code isn't perfect and may be at fault, as it sets that arrogance accusation back a bit. Back on topic to interject ... I'm leaning to a design flaw as the BAD 'BOO BOO BOO HISSSSSSSSS' case seems to be when YOU think it okay and reasonable below. (more later)
The difference between me and the average poster here, is that I'd hopes by confronting you in July, the sounds thing in November and with those candid thoughts of others besides myself above, you would perhaps improve your listening and actually focus on the issues. (You're bann on this draft N3V wiki edit on a page which had been stagnant for months I just find childish. All you did with that is hurt the new customers--whom I'd hoped to have help for by Christmas!. There are after all, many here that shake their heads at your 'Wiki', usually with swearing attached! Tony Hilliam had to take his time to renew what I'd started--three months later. Good un, Chris! I actually set Trainz aside for near three months, as being not worth the time--because you clearly weren't going to smarten up. Not sure resuming is smart of me. HOPE you prove my faith is warranted.)
Instead you are almost certainly rushing to push TANE instead of fixing TS12 as all the complaints since a year ago have begged. On this I'm with John Weylan, Fix TS12, and especially the DLS, then resume development of TANE. Your lack of dealing with both the former expeditiously just stirs up anger each occurrence of getting burned again by either. I went off on you in November on the sounds thing after an extended session of error fixing. Unforgivable, the time you cost others with inaction and ineffectiveness. I'm unpersuadable on that point. Your failure to effectively terminate the DLS errors issue is your greatest error. Until you correct that boondoggle, I'm going to forever have trouble seeing you as a true professional, the ceiling tops out at 'promising bush-leaguer'; you have talent and skills, but cogent priority setting seems vastly deficient. (In short, every time we get a new error from the DLS, or the performance dragging in TS12--we get P.O.'d all over again. To not bog this thread down, I'll post some concrete steps you can take immediately elsewhere in the next day or so. I've given it A LOT OF THOUGHT.)
[That's about a third... Good thing I excerpted to go on point again in the other thread!]
This continues from a discussion where I excerpted a bunch of emails that pointed out there were quite a few unhappy with the N3V status quo in TS12, most quoted being software savvy like myself:
Perhaps. However, you should also keep in mind that:
* In this thread, well in advance of your post, we've already identified specific issues that we'd like to investigate further.
* We have a major project underway to overhaul the Trainz engine, specifically to bring it up to date for modern workloads.
If that's "arrogance" and "lack of focus" then so be it.
chris
NOT my comment, as with many in that pistache. Just the way the wind blows from some other software people I network with, not all of them in Yesterdayz Trainz, either. Personally, I figure you've got a bit of PTSD, and should have been relieved of your "FACE" duties here on the forum several years ago. MANY of your answers come off as snippy, juvenile, and dismissive, and as the poster noted above, you run and hide often enough to be twitted about it.
As chief software geek, you have better things to do, I'm sure, and frankly your lack of sensitivity just alienates the people because your impatience shines through. People usually refer to that as arrogance, and believe it or not, I usually defend you on that. Actually, I defend you quite a bit. Mostly I point out that that appellation is not quite accurate, and you have other things you're balancing. As a designer I understand that very well. I'm heartened that you admit here that your code isn't perfect and may be at fault, as it sets that arrogance accusation back a bit. Back on topic to interject ... I'm leaning to a design flaw as the BAD 'BOO BOO BOO HISSSSSSSSS' case seems to be when YOU think it okay and reasonable below. (more later)
The difference between me and the average poster here, is that I'd hopes by confronting you in July, the sounds thing in November and with those candid thoughts of others besides myself above, you would perhaps improve your listening and actually focus on the issues. (You're bann on this draft N3V wiki edit on a page which had been stagnant for months I just find childish. All you did with that is hurt the new customers--whom I'd hoped to have help for by Christmas!. There are after all, many here that shake their heads at your 'Wiki', usually with swearing attached! Tony Hilliam had to take his time to renew what I'd started--three months later. Good un, Chris! I actually set Trainz aside for near three months, as being not worth the time--because you clearly weren't going to smarten up. Not sure resuming is smart of me. HOPE you prove my faith is warranted.)
Instead you are almost certainly rushing to push TANE instead of fixing TS12 as all the complaints since a year ago have begged. On this I'm with John Weylan, Fix TS12, and especially the DLS, then resume development of TANE. Your lack of dealing with both the former expeditiously just stirs up anger each occurrence of getting burned again by either. I went off on you in November on the sounds thing after an extended session of error fixing. Unforgivable, the time you cost others with inaction and ineffectiveness. I'm unpersuadable on that point. Your failure to effectively terminate the DLS errors issue is your greatest error. Until you correct that boondoggle, I'm going to forever have trouble seeing you as a true professional, the ceiling tops out at 'promising bush-leaguer'; you have talent and skills, but cogent priority setting seems vastly deficient. (In short, every time we get a new error from the DLS, or the performance dragging in TS12--we get P.O.'d all over again. To not bog this thread down, I'll post some concrete steps you can take immediately elsewhere in the next day or so. I've given it A LOT OF THOUGHT.)
[That's about a third... Good thing I excerpted to go on point again in the other thread!]
Last edited: