OK, who's been mucking it up this time ???

Stop making excuses for them Shane, they ain't gonna offer you a job, so let them come & make all the lame excuses they want themselves.
 
I don't need to make excuses. As you're probably aware, I run a website myself and encounter downtime issues first hand.

Shane
 
I may get in trouble with this post, but........

Perhaps one of our dodgy computer friends could find a way around the issue? Come on N3V. this is a real life issue that some of us have that needs to be sorted. Please do something unless Tane is prefect and in a couple of weeks we don't give a dog poo about it as we will be so happy using Tane! This is one thing that using Tane gives me hope that I will no longer have to moan about it each week to my Girlfriend.

Regards
CaptEngland. :(
 
I may get in trouble with this post, but........

Perhaps one of our dodgy computer friends could find a way around the issue? Come on N3V. this is a real life issue that some of us have that needs to be sorted. Please do something unless Tane is prefect and in a couple of weeks we don't give a dog poo about it as we will be so happy using Tane! This is one thing that using Tane gives me hope that I will no longer have to moan about it each week to my Girlfriend.

Regards
CaptEngland. :(

I know what you mean CaptEngland, as I get similar downtime issues myself with my own site. I'm helping to make T:ANE great the best I can though alongside everyone else.

We probably won't get much of a response until Monday though as it's a weekend down there.

Shane
 
Stop making excuses for them Shane, they ain't gonna offer you a job, so let them come & make all the lame excuses they want themselves.

You have two choices. Shutup, wait for them to get it sorted and then use your stuff or spend money to get a lawyer, court fees to sue them and time wasted with that. Up to you.
 
The problem stems from the use of Taddaemon , It started off as a simply program that stored the latest database in your install of Trainz , when the program crashed you could simply install the last good saved database and off you would go in a minute or 2 instead of waiting for it to do a rebuild . They then hijacked the program to become an integral part of Trainz and every version has gotten worse since . Then they bolted this DRM feature onto it and this is the fallout we have to deal with everytime there's a hiccup with the mothership !!

We can't blame TADDaemon, it's what has been done to it that's causing the problem. TADDaemon's main job is to manage access the database. In technical term a daemon is a background management process that's not supposed to get in the way that assists other processes to allow them to work better. A TADDaemon-like process is even found in MSSQL servers called the SQLManager Engine. There are many others for various database programs including those by Oracle, HP, IBM, and others.

With TADDaemon operating the way it should, not with this validation process, we can actually do multiple things with the database such as run Content Manager at the same time, and even install content as well as be searching for content in Surveyor, without a severe lock up or hang. If we were to attempt anything like this without a database manager, whether it's called TADDaemon or not, we would have file access violations and lock ups. This is why we see those lock attempt messages occasionally in the console window when downloading and viewing content. This is multiple TrainzUtil processes attempting to access data at the same time, and TADDaemon is stepping in as the overseer and allowing one process at a time to do its job.

That said with the implementation of DRM-controlled DLC and SP1 updates, something broke the code. The checking online code appears to be overly sensitive to changes and updates, and this was never addressed in TS12. According to the power's at N3V, the issue has been resolved in TANE, or it isn't as bad so let's hope this is and maybe they can come up with a solution for us TS12 users as well.

John
 
You have two choices. Shutup, wait for them to get it sorted and then use your stuff or spend money to get a lawyer, court fees to sue them and time wasted with that. Up to you.

There is a 3rd choice, those of us getting shafted with N3v's policies can take our money elsewhere, the way things are with DRM etc. I sure ain't gonna buy T:ane.
 
I think T:ANE is what we will be looking forward to seeing. So as long as the content works, that's mostly all that matters, unless T:ANE get's pushed off till August, which I do not think will (or should) happen.
 
That's your choice. For me, Tane has been an excellent upgrade already. Good luck
T:ANE is awesome, even with a few rough edges which will be smoothed out. I relate to this thread after having the same frustrations with TS12. Now using T:ANE exclusively - Trainz IS FUN AGAIN! Running under Win 10 Build 10074 (just-released Nvidia drivers installed yesterday).
 
Thanks Malc.
That's good to know.

I have a load of DLC Payware that came with the bundle, some of which I would like to use (like Murchison 2, and a few UK steamers and diesels), but there's no way I'm installing any of it.
I'll be building my route with just built-in content and any content I create.
Nothing from the DLS, and no payware installed at all.
Hopefully that will mean less problems.

Incidentally, someone recently mentioned that TADDaemon isn't part of T:ANE.
I know that CCP isn't going to be there, and that they've updated CM a bit, but I thought TADDaemon was still part of it.
Just wondering if that was a rumour (or possibly wishful thinking).

Brian.

There is only one executable file in T:ANE and that is tane.exe, rebuilding the database here in T:ANE on average here takes about 11 seconds........ No way is it the same system.
 
Well things appear to have settled down for now. It's back to route building for me, although the nice sunny day today keeps calling me for a walk instead. :)

John
 
No I didn't, I bought TS12 for £10

Capture_zpski4wl4la.png


It's ok, N3V thanks you for your donation.
 
That must be why there are unknown dependencies on the Italy and Switzerland route I just D/L from the black pages. The KUID finder cant locate them anywhere.

Unknown Location: <kuid:2512:41>
Unknown Location: <kuid:30501:100008>
Unknown Location: <kuid:30501:100009>
Unknown Location: <kuid:30501:100010>
Unknown Location: <kuid:30501:100013>
Unknown Location: <kuid:30501:100014>
Unknown Location: <kuid:30501:100015>
Unknown Location: <kuid:30501:100016>
Unknown Location: <kuid:30501:100017>
Unknown Location: <kuid:30501:100018>
Unknown Location: <kuid:30501:100019>
Unknown Location: <kuid:30501:100022>
Unknown Location: <kuid:30501:100023>
Unknown Location: <kuid:30501:100024>
Unknown Location: <kuid:30501:100025>
Unknown Location: <kuid:30501:100027>
Unknown Location: <kuid:30501:100028>
Unknown Location: <kuid:30501:100029>
Unknown Location: <kuid:30501:100030>
Unknown Location: <kuid:30501:100031>
Unknown Location: <kuid:30501:100032>
Unknown Location: <kuid:30501:100033>
Unknown Location: <kuid:30501:100034>
Unknown Location: <kuid:30501:100035>
Unknown Location: <kuid:30501:100037>
Unknown Location: <kuid:30501:100038>
Unknown Location: <kuid:30501:100039>
Unknown Location: <kuid:30501:100040>
Unknown Location: <kuid:30501:100041>
Unknown Location: <kuid:30501:100054>
Unknown Location: <kuid:30501:100055>
Unknown Location: <kuid:30501:100056>
Unknown Location: <kuid:30501:100057>
Unknown Location: <kuid:30501:100058>
Unknown Location: <kuid:30501:100059>
Unknown Location: <kuid:30501:100060>
Unknown Location: <kuid:30501:100061>
Unknown Location: <kuid:30501:100063>
Unknown Location: <kuid:30501:101064>
Unknown Location: <kuid:30501:101065>
Unknown Location: <kuid:30501:101066>
Unknown Location: <kuid:30501:101067>
Unknown Location: <kuid:30501:101068>
Unknown Location: <kuid:30501:101069>
Unknown Location: <kuid:30501:101070>
Unknown Location: <kuid:30501:101071>
Unknown Location: <kuid:30501:101072>
Unknown Location: <kuid:30501:101073>
Unknown Location: <kuid:30501:101074>
Unknown Location: <kuid:30501:101077>
Unknown Location: <kuid:30501:101078>
Unknown Location: <kuid:30501:101079>
Unknown Location: <kuid:30501:101080>
Unknown Location: <kuid:30501:101081>
Unknown Location: <kuid:30501:101082>
Unknown Location: <kuid:30501:101083>
Unknown Location: <kuid:30501:101084>
Unknown Location: <kuid:30501:101085>
Unknown Location: <kuid:30501:101086>
Unknown Location: <kuid:30501:101087>
Unknown Location: <kuid:30501:101088>
Unknown Location: <kuid:30501:101089>
Unknown Location: <kuid:30501:101090>
Unknown Location: <kuid:30501:101091>
Unknown Location: <kuid:30501:101093>
Unknown Location: <kuid:30501:101094>
Unknown Location: <kuid:30501:101095>


I'll check back when this is all solved and I imagine they will show on the DLC


Bill
Phx, AZ
 
Unknown Location: <kuid:2512:41> ----- Download this one here or at least search that website. http://cmkks.eu/news.php

Unknown Location: <kuid:30501:100008>
Unknown Location: <kuid:30501:100009>
Unknown Location: <kuid:30501:100010>
Unknown Location: <kuid:30501:100013>
Unknown Location: <kuid:30501:100014>
Unknown Location: <kuid:30501:100015>
Unknown Location: <kuid:30501:100016>
Unknown Location: <kuid:30501:100017>
Unknown Location: <kuid:30501:100018>
Unknown Location: <kuid:30501:100019>
Unknown Location: <kuid:30501:100022>
Unknown Location: <kuid:30501:100023>
Unknown Location: <kuid:30501:100024>
Unknown Location: <kuid:30501:100025>
Unknown Location: <kuid:30501:100027>
Unknown Location: <kuid:30501:100028>
Unknown Location: <kuid:30501:100029>
Unknown Location: <kuid:30501:100030>
Unknown Location: <kuid:30501:100031>
Unknown Location: <kuid:30501:100032>
Unknown Location: <kuid:30501:100033>
Unknown Location: <kuid:30501:100034>
Unknown Location: <kuid:30501:100035>
Unknown Location: <kuid:30501:100037>
Unknown Location: <kuid:30501:100038>
Unknown Location: <kuid:30501:100039>
Unknown Location: <kuid:30501:100040>
Unknown Location: <kuid:30501:100041>
Unknown Location: <kuid:30501:100054>
Unknown Location: <kuid:30501:100055>
Unknown Location: <kuid:30501:100056>
Unknown Location: <kuid:30501:100057>
Unknown Location: <kuid:30501:100058>
Unknown Location: <kuid:30501:100059>
Unknown Location: <kuid:30501:100060>
Unknown Location: <kuid:30501:100061>
Unknown Location: <kuid:30501:100063>
Unknown Location: <kuid:30501:101064>
Unknown Location: <kuid:30501:101065>
Unknown Location: <kuid:30501:101066>
Unknown Location: <kuid:30501:101067>
Unknown Location: <kuid:30501:101068>
Unknown Location: <kuid:30501:101069>
Unknown Location: <kuid:30501:101070>
Unknown Location: <kuid:30501:101071>
Unknown Location: <kuid:30501:101072>
Unknown Location: <kuid:30501:101073>
Unknown Location: <kuid:30501:101074>
Unknown Location: <kuid:30501:101077>
Unknown Location: <kuid:30501:101078>
Unknown Location: <kuid:30501:101079>
Unknown Location: <kuid:30501:101080>
Unknown Location: <kuid:30501:101081>
Unknown Location: <kuid:30501:101082>
Unknown Location: <kuid:30501:101083>
Unknown Location: <kuid:30501:101084>
Unknown Location: <kuid:30501:101085>
Unknown Location: <kuid:30501:101086>
Unknown Location: <kuid:30501:101087>
Unknown Location: <kuid:30501:101088>
Unknown Location: <kuid:30501:101089>
Unknown Location: <kuid:30501:101090>
Unknown Location: <kuid:30501:101091>
Unknown Location: <kuid:30501:101093>
Unknown Location: <kuid:30501:101094>
Unknown Location: <kuid:30501:101095>




Bill,

It appears the big list of kuid;30501:xxxxxxx is not available anywhere public. The one item, highlighted in bold is available from the website listed in the search. I put the link and hopefully you can use that.

I did a search using this nifty website and came up empty handed.

http://www.trainzkuidindex.com/eng/Assets/search
 
These are Auran assets - I imagine that the work to get the DLS updated in preparation for T:ANE release has had a side effect of some things disappearing. This is possibly (stab in the dark until Monday when the content guys will investigate fully) why the validation issues have been seen as well - with items going missing any dependant assets (that rely on the missing ones) will require validation.
 
Back
Top