|
Post by james37611 on Apr 29, 2020 11:47:41 GMT
Hello,
I am thoroughly looking forward to making a District Line 2018 Rush Hour scenario pack, having done one for the Met, the District one so far is more interesting!
I've only just started on it with teo scenarios, I haven't used the announcements as I can't figure out how it works, I copied the work order of the T/OP S7 scenarios but when I do it in my own ones, no sounds play, not sure how it knows what your destination is either. Is there a guide somewhere so that we can use these in our own District scenarios or are they scripted only for the T/OP scenarios?
Doesn't matter if they cant be used for custom scenarios.
My main point of this post is I just started an Ealing - Upminster one, to end at Gloucester Road, but I see the next stage is already in testing and I'm not looking for an exact ETA, but I assume this may be a release this year?
I only ask as if the extension is due soon, I'll hold off creation until 2.1A is released.
I have done Wimbledon - Edgware Road and back so far, and it really is astonishing freeware!!
Thank you for the hard work!
James.
|
|
|
Post by Eddie on Apr 29, 2020 12:23:09 GMT
James,thanks for your kind words, it is much appreciated by all the team. As regards creating scenarios, you would be well advised to wait until 2.1a is released before creating scenarios that go to or from Gloucester Road. The Wimbleware should be fine however. The reason no sounds play in your scenarios is probably because you have no wavs in your en folder. That is where the audio is kept. We have a library of audio sounds for the District S7 and the Met too, plus there is something in the pipeline. The route has the necessary markers for announcements built in, but the key is our audio library. You could, however, create a library of your own..............
|
|
|
Post by Jimi on Apr 29, 2020 12:45:06 GMT
I believe James is TubeMad on UKTS, and if so he's been around about as long as we have :-) James the reason to wait for 2.1a (which won't be long) is it provides modifications and extensions at GRD that allow us to continue building towards Tower Hill, etc. but also allows folks to build scenarios using GRD that will then still work in the future. If you were to build one now, we can't guarantee it will work with future route builds as locations, markers, portals, etc. are being changed or added in v2.1a. As regards the audio in the TopMan scenarios... As Ed notes, we have added audio trigger markers into route v2.1 at key locations approaching and within station areas. Using these as Via points in the train timetable (task list) means the event completes when a train passes over them and that causes an event trigger. The event number (unique for each announcement) is passed to a chunk of LUA code within the ScenarioScript.LUA file. The LUA decodes the event number and then calls a TS system function to play the related WAV file, that is located in the scenario's En folder. All of that capability has been around for quite a while, so I'm not really giving away secrets by describing it. There are a LOT of clever things one can do with scenario scripting - our latest version (in dev/test) also causes triggered weather changes during the scenario. What did take us a lot of time is the careful positioning of all the audio trigger points, and developing the audio so it matched prototypical LUL announcements, and we used the initial set of TopMan scenarios as a proof of concept. And as Ed also notes, there is more to come...
Armed with the description above, you could make your own WAVs and populate the En folder and cause them to be triggered via our ScenarioScript.LUA code. And we will keep everyone informed about v2.1a. As we have been dev/testing the next set of scenarios, we have had need to make small detail changes to the route, signals, etc. That work is onging.
|
|
|
Post by james37611 on Apr 29, 2020 15:37:45 GMT
Thank you very much! That explains why the sounds aren't working, I didn't think it could be just adding the waypoint and trigger instructions that would make it work! Jimi - Yes it is indeed tubemad from UKTS, playing simulators since Cab View Driver, Mechanik and BVE1! Thank you very much for your advice, I shall put the project on hold, as I say not worried about dates, but I wouldn't want to make 20 scenario's, then find I've got to re-write all 20 scenario's, thought it would be best to check first! I know it will be worth the wait, always amazes me how some aren't interested in freeware because it won't be any good, quite the opposite when you compare this and JT's Met! I found writing on JT's Met line was rather difficult, in that it just wasn't flexible, and a vast amjority of the sidings, which are used by S8 Met stock, is just there for show and not to be used. Then couldn't even be bothered with an AI 1996 stock for the Jubilee section Compared to this, which has all the operational flexibility of yards and depot's that can be used, and appropriate AI stock! Countless times I've done Paddington on C Stock's to either Earls Court or Edgware Road, and all recognisable on this route The next phase will be well worth the wait! Just out of interest, will there be more portals on the Wimbledon line? Just noticed when I was doing Wimbledon from Edgware, the nearest exit point to get rid of AI was Gloucester Road. Doesn't need a lot of portals though Thanks again guys! James.
|
|
|
Post by Eddie on Apr 29, 2020 17:34:04 GMT
Ah Portals.................... don't mention Portals.............I just did , but I think I got away with it.
|
|
|
Post by Jimi on Apr 29, 2020 17:36:49 GMT
James - here's the latest portal list from the in-development v2.1a. Significantly more than before. I'll update the route docs with the final list for 2.1a. I've only listed the "inbound" (entry) LU portals. In every case there are companion outbound (lose the train) portals nearby.
LUL:
Barons Ct (Picc) WB - train spawns in the pipe in rear of signal A654
Rayners Lane (Picc) EB - train spawns in N Ealing EB platform in advance of home signal A102
Northfields (Picc) EB Fast - train spawns in rear of signal A498
Northfields (Picc) EB Slow - train spawns in rear of signal A497
Ealing Bdy (Central) WB - train spawns in rear of signal WL46
Ealing Bdy (DR) EB - train spawns in advance of signal WMX549
Edgware Road Circle Inner Rail WB - train spawns at end of track in the east tunnel in rear of signal OP1A Edgware Road Circle Outer Rail EB - renamed for consistency with other ERD portals and destination markers
Royal Oak H&C EB - train spawns at end of track in rear of signal TRX127 Olympia SB - train spawns in advance of signal A604 on the SB road of the double-tracked section
Gloucester Rd WB - train spawns in rear of signal EF265
Richmond (DR) EB - train spawns in rear of gantry signal GB16
Wimbledon (DR) EB - train spawns in rear of signal W374 West Kensington (DR) EB/WB - in or out. Sited between WKN and BCT roughly abeam (James May word) the pipe
NR: Gunnersbury (NLL) - NLL portal WB (In) / EB (Out) Richmond - From Putney WB, Putney EB, From Kingston EB, Kingston WB Ealing Broadway (GWR) - EBY GWR EB/WB Slow/Fast [Inbound] Olympia/Fulham Broadway - From Shepherds Bush Inbound, To Shepherds Bush NB portal, From Clapham Jct Inbound, To Clapham Jct SB East Putney (SWT) - East Putney SWT WB (in) / EB (out) Wimbledon - Croydon tramlink NB / Elmers End, From Sutton EB / To Sutton, Guildford slow / Portsmouth fast, Raynes Pk fast/slow, Raynes Pk EB fast/slow, From Streatham to Wim Inbound / Streatham, From Waterloo slow / fast up, To Earlsfiled slow, To Waterloo fast down
|
|
|
Post by Eddie on Apr 30, 2020 18:05:16 GMT
Some of these portals ( inbound ) exhibit strange behaviour. The one at Ealing Broadway and North Ealing being two. The train spawns but then loops back after passing some signals. Eventually if you have more than 1 service in those 2 portals you will end up with an AI collision. We tried moving these slightly, moving them a lot etc etc. But with no success. So not all of them work properly, there is no science , it is witchcraft, but we did our best.
|
|
|
Post by james37611 on Apr 30, 2020 23:53:13 GMT
Thank you for the list most appreciated! Eddie - Maybe an issue with Portals in general? Are you doing it with different services? Not that I've used Portals much, but I found they seem to work with a simple A-B short route, anything else is out the question! I did some services starting from a Portal, one took a Fast Line, the next took the Slow Line over the nearby crossover, it didn't like that! The slow service derailed. Then I altered it to crossover elsewhere, then it got stuck at a red and the next AI train crashed into it, then I decided not to bother with the portals for entries!! This was at Bedford on the MML Route, the thing is you needed the portal as the 'run off' track was so short, you couldn't have a static fast and slow train out of sight ready to overtake you. Also, not reporting this as an error as I have no idea if the signal's are like that as it may well be the case, but for the last signal coming into High Street Kensington, from Notting Hill Gate, does it have a repeater? On my scenario from Edgware you follow a Circle to HSK. I know it's in front, but I left Notting Hill, next signal was green, passed that, round a left blind curve, and round it to see a red ! Slammed on the brakes but just, and only just, whacked the tripcock. There was no previous yellow aspect, is this how it is set up in real life? If so I would assume in real life you'd take the curve slower than line speed in case, driving on sight rather than relying on repeaters? Cheers, James.
|
|
|
Post by Jimi on May 1, 2020 3:20:47 GMT
I do the signals, so I'll answer, having re-checked my charts. There *is* an error approaching HSK WB, but not quite as you thought. We're not missing a repeater, but rather have a wrong signal on approach to HSK.
What we have now going WB from NHG is A162 (NHG starter), about 500m later at the end of the straight is A158, then E300/RED3 on the curve (the one you found red), then RED4 on the approach, then ED4 (HSK starter).
The error is that repeater RED4 on approach should be a semi home ED3, which is logical as we have ED300 (speed control) with co-located RED3 (home signal repeater) in rear - so we should expect ED3 (home) next. No idea how I goofed that, but I have fixed it so it's now dev current and will be in the v2.1a build.
What happened to you is there was a train ahead in HSK platform, but no home signal protecting it in rear at platform end as there should be. ED300 was acting like an outer home but was wrongly including the platform area in its track circuit, and to compound the error was on a curve and had no repeater to warn you it was red. (As my father used to say, if the worst comes to the worst...we're screwed).
Normally ED300 would NOT be red, once you reduce speed to 25 on approach, and it's designed to reduce train speed (on the 1:70 downgrade) approaching HSK home. So once you reduce speed you'd expect green over yellow (ED300/RED3) if there was a train in the platform because ED3 (home) would be red. And you'd be slower (25mph) passing ED300 and now have plenty of warning of the red home and room to stop at that speed.
Short version: I have fixed it by replacing the (wrong) RED4 with ED3 (home) and it will all work as LUL intended :-) Route knowledge would tell you that you needed to slow after A158 approaching the curve (25 limit plus ED300 speed control), after which you'd be fine as RED3 would alert you if home was red and you have room to stop in time.
Good catch James. Thanks!
|
|
|
Post by james37611 on Mar 2, 2021 18:54:28 GMT
I do the signals, so I'll answer, having re-checked my charts. There *is* an error approaching HSK WB, but not quite as you thought. We're not missing a repeater, but rather have a wrong signal on approach to HSK.
What we have now going WB from NHG is A162 (NHG starter), about 500m later at the end of the straight is A158, then E300/RED3 on the curve (the one you found red), then RED4 on the approach, then ED4 (HSK starter).
The error is that repeater RED4 on approach should be a semi home ED3, which is logical as we have ED300 (speed control) with co-located RED3 (home signal repeater) in rear - so we should expect ED3 (home) next. No idea how I goofed that, but I have fixed it so it's now dev current and will be in the v2.1a build.
What happened to you is there was a train ahead in HSK platform, but no home signal protecting it in rear at platform end as there should be. ED300 was acting like an outer home but was wrongly including the platform area in its track circuit, and to compound the error was on a curve and had no repeater to warn you it was red. (As my father used to say, if the worst comes to the worst...we're screwed).
Normally ED300 would NOT be red, once you reduce speed to 25 on approach, and it's designed to reduce train speed (on the 1:70 downgrade) approaching HSK home. So once you reduce speed you'd expect green over yellow (ED300/RED3) if there was a train in the platform because ED3 (home) would be red. And you'd be slower (25mph) passing ED300 and now have plenty of warning of the red home and room to stop at that speed.
Short version: I have fixed it by replacing the (wrong) RED4 with ED3 (home) and it will all work as LUL intended :-) Route knowledge would tell you that you needed to slow after A158 approaching the curve (25 limit plus ED300 speed control), after which you'd be fine as RED3 would alert you if home was red and you have room to stop in time.
Good catch James. Thanks!
Jimmi and Eddie I have had a bit of time away from the sim recently and have come back and installed V2.2, when I have the time very soon, I'll be giving it a blast! Now is it safe to make a scenario pack? Bearing in mind it will probably take me a good 2-3 months to do that, and by that time Phase 3 might be down the road?
|
|
|
Post by Jimi on Mar 2, 2021 19:51:08 GMT
Phase III is a ways out yet. We're as far east as Westminster as regards stations. I'd go ahead and do a few scenarios based on v2.2. I'd love to see some!
|
|
|
Post by james37611 on Mar 3, 2021 10:48:54 GMT
Phase III is a ways out yet. We're as far east as Westminster as regards stations. I'd go ahead and do a few scenarios based on v2.2. I'd love to see some! Thank you for confirming that Jimi! Had a go in the S7 Top Man Wimbledon - Edgware Road and Edgware Road to Richmond, just absolutely stunning!! One thought on speed limits, and maybe its been thought of but doesn't work so I don't know as I've never dabbed into the route editor, but do the speed board sign objects have to be where the change of speed limit is placed? Is it possible for a speed change from, say 20mlh to 30mph be put in on the track, and the 30mph board scenery object placed so many meters down the line, so that when you reach the board the new speed limit is changed in the HUD?
|
|
|
Post by Jimi on Mar 3, 2021 17:30:26 GMT
I realize you are trying to adjust things so the operator can accelerate as front-of-train passes the sign. Doesn't work well, especially if there's something ahead (junction, etc.). Just ignore the summary "exceeded speed limit 123 times" messages. Note that the limit applies to speed reductions too, so if we moved the sign or marker those would be messed up. I'd rather know exactly where the limit change is (it's usually for some kind of infrastructure reason) and drive accordingly. Personally I accelerate as front of cab passes, as LUL prescribes.
Regarding scenario creation... V2.2 (with the 2 hot fixes we've posted in Ed's DropBox) is a solid base to create on, bar the one error we're aware of at the ERD sidings and related shunt signal, discussed in another post. We will fix that for Phase III. All other moves, sidings, depot roads, etc and signals should work as expected.
And many thanks for your kind comments. We put a lot into the Top Man and EC scenarios, and capitalized on the large number of portals we'd added in v2.2. Those let you add and remove AI traffic so the overall resource load on the sim remains reasonable without too high of an AI train count.
|
|
|
Post by james37611 on Mar 24, 2021 21:52:13 GMT
I have just tried to make a start, looks like there will be no pack from me, sorry In fact there won't be any scenario's for this from me I've got 90 - 95% of the first scenario done, but now I can't get into it, just memory dumps every time, probably to do with the S7 stock, same with the Met line as I can no longer run that anymore either. If someone wants to finish this scenario I can send it over, you just need to S7+1 Advanced, and the District, Circle and H&C destination versions from ATS. I have the 2017 Working Timetable PDF as well.
|
|
|
Post by Eddie on Mar 25, 2021 16:52:50 GMT
Don't despair just yet James.............. we too had the OOM issue that seems to afflict the S7+1 stock. You can change the driver train quite easily for a D78 which won't memory dump on you. Just set a D78 consist alongside your player S7+1 at the starting position. So, you'll have your player train with all its timetable movements sitting there alongside the newly laid D78. Now just click on the S7+1 driver icon and holding the left mouse button down drag it over to the D78. Now the timetable is on the D78, but of course the platform is now changed, so delete the S7+1 consist ( use the whole consist button ) Drag the D78 over to the original starting platform. Now save and press drive. Once the cab loads, press restart and see if you can now run the scenario....................
If it runs you can carry on building the scenario until it is complete. One thing we found, is that if there is any issue with the TS despatcher ANYWHERE within the scenario, even on an AI train, you will get the OOM dump, even with the D78. Once you have checked it ( check it also in TS Tools ) and it is clean, change the D78 back to your S7+1.
We had scenarios go "bad" like this on us and we often found it was caused by an AI movement which was unintended, somewhere else in the scenario.
|
|
|
Post by Eddie on Mar 25, 2021 17:15:54 GMT
If you could upload the scenario to your dropbox or mediafire we are more than happy to try and help you troubleshoot it.
|
|
|
Post by Jimi on Mar 25, 2021 17:19:51 GMT
HI James, Ed gives excellent advice above and I'd echo it. Also a few questions to help us understand the issue better.
When does the scenario dump? In the editor or when trying to run it? What was the last change/addition you made?
Why will the Met no longer run? What changed to cause that? Are you running the latest updates to the Met and S7?
Can you run any/all of our TopMan S7 scenarios? How about the Emma Clark scenarios (if u have them)?
Are you running the 32-bit or 64-bit TS? When editing? When running the scenario?
In addition to Ed's suggestion re swapping S7 to D78, also try clearing the cache. Be aware that re-starts TS in 32-bit. Keep the faith - we'll help diagnose....
|
|
|
Post by james37611 on Mar 25, 2021 22:18:59 GMT
Thank you guys, honestly it's just because I can't run the Met that made me wonder that it was probably the problem, I hope not as I was looking forward to making this! I had almost done all the SB services from Edgware Road, the next evening I loaded up the scenario in the editor, chose to fly to Earls Court as that's where I wanted to be, and then I had a memory dump. Since then I get a dump as soon as it's loaded, I can't place a D78 stock beside as I only have about 2 seconds when it loads and crashes out. I can't test drive as I haven't placed an end marker or set the train as player. In question as to why the Met won't load anymore, I have no idea unfortunately, I had it running fine, then I uninstalled TS in favour for MSFS 2020, I was set to be doing virtual flying instead, but in the end it seemed a bit time consuming, and £££ were popping up for this and that, and looked to be a very expensive hobby in the long run, not that money is a problem but spending over £50 for something I may only use twice, when I could spend less on a TS and get more out of it. So I reinstalled TS, got the Met line back up and the S7+1 and S8 stock, tried the scenario's but I get the OOM 2 seconds on loading. I have tried a couple of the T/Op supplied S7 scenario's and they work fine, though some of the AI is C or D stock as well, would that make a difference, as all mine are S7 stock though they are the AI District version. I am using the 64-bit editor. Maybe an AI issue otherwise then? Here is the link to the .rwp file: www.dropbox.com/s/hgs7saz4yf5niio/LUDistrict-Scenario.rwp?dl=0Just need to see if you can get it to load in the editor and not memory dump as soon as it loads, then we can hopefully narrow down some ideas. Thank you!! James.
|
|
|
Post by Jimi on Mar 26, 2021 15:16:35 GMT
A few first blush thoughts and suggestions, having grabbed, edited and run it.
I don't think you wan to use Timetabled scenario class. It's not needed to set timetabled actions, and it's normally only used when you want a train to arrive and then the player to take it over. We have 2 scenarios that do that. If that *was* your intent, then fine - else set it to standard class. You can do that via TStools, or by editing ScenarioProperties.xml. Search for the line beginning <ScenarioClass and change the embedded string from eTimetableScenarioClass to be eStandardScenarioClass. You can still make selected actions timetabled by checking the appropriate box in the action properties. That will cause a train to be held to the specified departure time.
I'm concluding that T070 is meant to be the player train although it isn't yet designated as such.
I first loaded into the editor (no issue) then browsed the timetables, then ran it as-is. T070 (at WIM) pulls forward to the starter and opens doors. Other S7 arrives in P1. T070 starter goes green, etc. so all appears OK, and is running fine as far as I can see.
16 active AI trains may be a bit much for some systems, and you may wish to load some that are out of sight of the player via portals at the appropriate times.
I'm now going to change the scenario to standard and make T070 the player train and try to run again...
UPDATE:
Modified the scenario to be Standard, made T070 the player train, added Putney Bridge 1 destination to its actions, saved and ran. All behaved as expected. I see several AI trains approaching and glancing at the 9 map shows others moving or ready to do so.
I'm going to pass this over to Ed and ask him to DropBox host it so you can download and try again. My gut says something isn't quite right with your system if you can not now run Met, and if this scenario fails to load. If you can run our other VDL scenarios but not this one, then it's possible you have some settings that are draining resources. OOM errors are a major pain and (I feel) not fully understood by any of us. Not even DTG.
|
|
|
Post by Eddie on Mar 26, 2021 18:48:34 GMT
Had a look at Jimi's modded Standard timetable version James, and it loaded fine into my 32 bit Editor. Only use the 32 bit Editor to create scenarios. Never, ever use the 64 bit version. If that crashes whilst in the Editor it can break the whole route's track.bin file. Don't ask us how we know this, but trust us on this. The other thing I noticed is that you've used final destination instructions for all your AI services. This is a real no,no.
Only the player train has a final destination. Use Pick up passenger instructions at stations and just leave them there like that. Use Go To/ Stop pointy hand instructions for portals. Your player train was locked at Putney and impossible to go further because of this. I took out all your final destination instructions and Jimi will now test to see if he can drive to Edgware Road P3. The other no no you've done is placing a lot of your AI trains in platforms. Don't do this as the starter signal and home signal get locked on initialisation of the scenario. Always place your AI trains on clear track away from platforms. I haven't moved them , but you should.
Its nice to see someone actually building decent scenarios for our route and this looks very promising, so don't throw in the towel. You really need to read our Creating Scenario Guide for avoiding all these pitfalls. It's a huge subject and many people fall by the wayside because of a lack of good documentation in the Scenario Editor.
|
|
|
Post by james37611 on Mar 28, 2021 16:46:21 GMT
Interesting, for all the years I've done scenario's I learnt a few things there, thank you very much!
I never knew you could just use the arrow to a portal and it would work, all of what I've done is just what I've tried to work out myself and ended up as the format. I've only ever used AI starting at portals once, and concluded to an AI crash so never trusted it again. To be honest I couldn't set much AI from the portal for this scenario, as there aren't any portals to start on the Wimbledon branch (SB ones anyway)
Can someone set T070 as the player and make an end point so I can see if it runs as a player on my machine, just to try and narrow some things down. I have tried 32 bit but am still getting OOM on loading up.
Oddly enough pre-re installation I had made two scenario's on the previous District version, same S7 stock throughout, same set up as I have in this one, and worked perfectly. Same with the Met.
I have also just finished making a South London to Brighton scenario with a lot of Armstrong Powerhouse stock, and full scenery detail, and is whizzing through this in the editor with no stutters or crashing out, had the editor in 64 bit running for a good 4 hours solid, on my old PC on 32 bit it would crash after an hour or so, but no problems with this
|
|
|
Post by Eddie on Mar 28, 2021 17:49:04 GMT
So my advice would be to run the Editor in 32 bit. Drive it in 64 bit. That is our rule. There is a NB inbound portal at Wimbledon ( near the home signal gantry ) and it spawns trains just fine. One of the good solid ones. Take a closer look. For Southbound we put a portal on the Inner Circle beyond Edgware Road and there is a portal on the EB H&C which you can use to spawn EB services then reverse them in the tunnels beyond Edgware Road. I also make use of the two sidings there as well. Here is my modded version of your scenario James, with player train T070 routed all the way to Edgware Road P3 which is the preferred platform when clear. You'll need to move all your AI stock ( use whole consist button ) out of the platforms and clear of any junctions as well or you will get signal lock ups. Just extract the zip to your District Scenarios folder ( move your one out of the way ) starts with d6d61234 www.dropbox.com/s/sbkx0taavqc3lvk/Eds%20mod%20version.7z?dl=0Keep your version safe, then look at your AI timetable view and compare to see what I did...............only way to learn. I do agree it's likely the S7+1 is the cause of the memory dumps. Our stocks work fine.
|
|
|
Post by james37611 on Mar 29, 2021 8:56:07 GMT
Thank you Eddie I shall give that a go later or tomorrow after work. I can't even get in it in the 32 bit editor, but I thought I'd at least try and drive it so I can see if its the S7 causing the OOM (to be honest its likely especially when the S8 is playing up on the Met) I'm aware of the NB portal, what I meant was to see some of the Wimbledon services on time, they need to start south of Earls Court. But yes not all of them need to, maybe otherwise I could try an older D stock and S stock based one instead
|
|
|
Post by Eddie on Mar 29, 2021 17:33:59 GMT
In order to see trains coming towards you as you leave WIM put a train just south of Wimbledon Park, ( you can route that into the SB portal). Then put trains down 4 stations apart. Have them start at the same time as the player service. The trains from Edgware Road might need to be delayed by 10 minutes or so. If you start them from portals SB make sure the headway between them is about 4/5 minutes. That's a rough idea of how I schedule our scenarios. For interesting meets you can tweak individual trains timing too. We prefer to change all our services from the default 75% performance to 90% or even 95%, so the trains run closer to line speed. Be aware that can cause conflicts though , so do one train at a time and see if red error boxes occur. Make only 1 change at a time and if it goes pear shaped back track the last thing you did. I always build my scenarios with just the player train to start with and check it runs. Then I add AI services 1 train at a time. Sometimes you can push it just too far , so take out the last service you put in. Always keep back ups as you go.
|
|
|
Post by james37611 on Mar 30, 2021 20:13:40 GMT
Eddie, Thank you very much for your time, I have definitely now putting it down as the S7 stock. I can load the scenario as above, but if I move the camera or change view it throws me out. And I still get the same thing as soon as it loads in the editor, so I shall ditch this scenario and try again when the Creating Scenario Guide is released I forgot to mention, I hope you I did not come across at saying there was a problem with your route or creations, or claiming I know what I'm doing, as I was not intending to (as I say, that's if I did! That's the problem with text!) Thank you so much for your time in responding and for the long write ups, it's most appreciated! James.
|
|