Suggestion re Assets

[alanch]

Hi Matt

Sounds like you are getting somewhere with this, so many thanks

I don't know if this is relevant, but I've discovered that finding scenarios is difficult, because there is no scenario category in the file library - so authors categorise them as the route, or as a type of loco. Would it be difficult to add scenario as a category, and then re-categorise existing files?

[NeutronIC]

The correct category for scenarios would be "activities" since that maps to the equivalent in the MSTS world.

Unfortunately the file library as it stands can only cope with one concept - if I add "scenarios" then MSTS files get that too.

My intention is to remove this inflexibility so that RailWorks files can have their own set of fields unique to themselves - indeed, that will go down to the file type, so that routes can be different to rolling stock, diesels different to steam and so forth.

On the very long list of jobs to be done.

Matt.

[NeutronIC]

OK, i'm done for the day, nearly dinner time and then I have to drive back home so not likely to get much more done now.

Progress has been excellent.

Client is now integrated with the Server.

Login and Logout work.
Retrieving and updating the collection hierarchy and list works.
Rendering the collection tree works.
Select a collection to view its contents and details works.
The server has the concept of subscribing to a collection and the client can query this and find out if you're subscribed to a collection and update this in the client appropriately.
The client has subscribe/unsubscribe options but that's where the trail runs dry.

I've got much of the framework in for the client/server interface to support add/remove subscription capability, but nothing actually implemented in the methods.

Once add/remove is done, the next job is to have the capability to scan through your subscriptions, look at some local list and see what needs to be downloaded - once i've done that, next job is to set up the downloader and actually download files, lastly I need to then install them.

So major progress, hopefully another week or two will see the remaining bits done to prove the concept and then we'll see how it is.

There are of course still server-side considerations for the web site itself, like being able to assign files to collections but initially i'm going to just manage that manually directly with the database. Once things are settled down and proven to work I can update / add screens to manage and configure that side of things.

If there's any artists in here that are good at Icons then shout, the client needs some serious prettying up.

Matt.

[Otterbear2]

Hey Matt,
Any news?
Just downloaded Whales and Borders (Again), only to discover I need IOW to run it. ahhh!
I must be getting tired.
Cant wait till I can tell ahead of time what I need.
Looking forward to the finished work.
No rush...just wondering.
Dave

[kirkheath]

A dvd would be a good idea except the trouble is that with it being constantly updated this means you would require to purchase a new DVD every two to four months IMO. I think that route authors could email the authors of assets used and have two rwp install files. One is the route and scenarioes. another is all the extra 3rd party assets.

[alanch]

Hey Matt,
Any news?
Just downloaded Whales and Borders (Again), only to discover I need IOW to run it. ahhh!
I must be getting tired.
Cant wait till I can tell ahead of time what I need.
Looking forward to the finished work.
No rush...just wondering.
Dave

You will need to look here http://forums.uktrainsim.com/viewforum.php?f=332 for more news on Matt's project.

Are you feeding the Whales?

[Otterbear2]

Are you feeding the Whales?

LMBO!
Thanks for the info.

That's embarrassing,...My family originates in Wales. Kidwelly, to be exact...we lived in the castle back then, I'm sure of it.
My Grammar aint what its 'possed to be these days.

[clockmaker]

Matt wrote

This is one of the misconceptions of "requirement" that i've seen a number of times. IMHO a Route only REQUIRES items which are non-rolling stock. I.e. if you package your route up with only scenarios that use default stock (even if it's just a single default free roam) and then package your specific scenarios separately, then anyone can enjoy your route without Isle of Wight -

Am I correct in thinking that you are saying that provided a route does not use any of the IOW rolling stock then it should be possible to use that route but without the IOW scenery ?
If I am correct in understanding your comments then I have to say that with my computers, with the Wales and Borders route, that is not correct.
I have installed that route in two computers, one with Vista and one with XP, neither initially having IOW installed.
In both computers the program crashes when approaching the location of a water tower or more quickly when scrolling the 2D map with all filters ticked. I believe the problem is due to the IOW fuel point assets being missing.
If I untick the fuel filter only, in the 2D map, then the program does not crash when scrolling the map.
All is OK when IOW route installed.
If I remove the files for the fuel points only, from the IOW assets, again the route crashes. In Vista I get RailWorks Proc error. In XP, the computer just locks up and has to be turned off.
Norman

[NeutronIC]

Hi Norman,

No that's not quite what I meant

My intention was to say that when packaging a route up for distribution, the only things that are *required* to make it work for other users are all the scenic dependencies - rolling stock should *not* be a dependency because scenarios can be distributed separately, thereby easing the burden on those trying to find the required assets and also reducing any payware requirement if you happen to have built payware scenarios with your route.

In some cases you *can* get away without having all the scenery installed, railworks will survive quite a lot of "damage" but there are some track infrastructure items that will cause it major headaches and exhibit the symptoms you mention.

So, all scenery items are definitely required, mandatory. Stock etc you can eliminate the dependency for by deleting the built-in scenarios if you so desire - my point was to try and encourage route authors to remove scenarios containing non-default stock so that the required list of downloads just to make the route work is reduced as much as possible - the scenarios can then be distributed separately with the list of stock required for each one, making it much more manageable to do in bite sized chunks.

Hope that explains it better

Cheers
Matt.

[Trainguy76]

So, all scenery items are definitely required, mandatory.

I think it's all track linked/ track based items are required.

For example, a missing texture for a building does not kill the route.

[clockmaker]

Hi Matt

Thanks for your reply. It means that for beginners ( or anyone in fact ) they still need to have IOW installed before, in this case, Wales and Borders will run.

RDN a great idea. Would have saved me a lot of time getting the assets for Wales and Borders. Hope you get it working and manage to link up to other sites that have asssets for download

Norman