{"id":885,"date":"2009-07-05T15:50:32","date_gmt":"2009-07-05T14:50:32","guid":{"rendered":"\/blog\/?p=885"},"modified":"2009-07-05T15:50:32","modified_gmt":"2009-07-05T14:50:32","slug":"3d-cabs-openbve-v1-1-0-development-branch-new-video-uploaded","status":"publish","type":"post","link":"https:\/\/railsimroutes.net\/blog\/openbve\/3d-cabs-openbve-v1-1-0-development-branch-new-video-uploaded\/","title":{"rendered":"New Video Uploaded: 3D Cabs (openBVE v1.1 Development Branch), 323 Interior, Watford Junction to Rugby Hi-Res"},"content":{"rendered":"

openBVE v1.1.1.0 (Development Branch), 3D cabs, and other stuff…<\/span><\/strong><\/p>\n

\"openBVEThe first release (v1.1.0.0) in the development branch of openBVE was made available a few days ago, and now v1.1.1.0 has subsequently been released — the development branch includes support for full 3D cabs with animated objects<\/strong>, and mouse controlled camera rotation<\/strong>. v1.1.1.0 also introduces driver’s head motion<\/strong>, which responds to acceleration and deceleration, as well as inertia.<\/p>\n

As many will no doubt have noticed, I’ve not shown much by way of screenshots or video of openBVE’s in-cab experience thus far, as personally, I’ve always viewed the existing 2D panel support as something of a legacy feature which didn’t really demonstrate openBVE’s true potential, so I’ve been waiting for this moment for a long time, and I have to say, it most certainly lives up to expectations and is quite simply fantastic! Applying emergency brakes has never been so much fun. \ud83d\ude09<\/p>\n

Firstly, releases in the openBVE development branch are intended for developers who wish to expermiment with new features and offer feedback before these are eventually incorporated into the stable branch. Development releases may contain undetected issues, and features are subject to change, which means the development releases aren’t entirely suitable for regular users and the less technically minded, however I strongly recommend that developers and advanced users take a look at the development releases. If you’re interested in examining the new 3D cab support, you can head over to the \u00bb openBVE homepage \u00ab<\/a><\/span> to download version 1.1.1.0, along with a demonstration 3D cab update for the 113-1000atccab train (look under Examples via the \u00bb Developing for openBVE \u00ab<\/a><\/span> menu). Please also read the \u00bb Changelog \u00ab<\/a><\/span> for a full list of alterations and new features.<\/p>\n

Anyway, I’ve spent around a week working on a 3D cab for the new class 323 EMU and Cross-City South v1.4, and I’m really pleased with the results so far. I’ve uploaded a new YouTube video to briefly demonstrate the immersive nature of a 3D cab<\/strong>, the added realism, and some of the animated object possibilities — animated traction\/brake controller, reverser and horn lever<\/strong>, working in-cab safety system indicators<\/strong>, simulated working headlights which give the effect of outside illumination (but see caveat below)<\/strong>, along with working in-cab illumination<\/strong>. I think the potential of openBVE as a cab based simulator can now be truly realised, and speaking personally, this has forever changed the way I experience openBVE routes, and as long as photo-realism is maintained in new 3D cab environments, I’ll likely not want to go back to 2D cabs now.<\/p>\n

This latest video was originally intended to show some other things I’ve been working on, so you’ll find many clips of the new 3D interior<\/strong> for the class 323, which includes seating<\/strong>, working television screens and lights<\/strong>, moving and streaking raindrop effects <\/strong>(inspired by the rain effects from Flight Unlimited 3), and ground illumination<\/strong> from the windows and pantograph sparking at night. The performance improvements which came with openBVE v1.0.7 also enabled me to capture some higher resolution video of Watford Junction to Rugby<\/strong>, of which many shots are included (and it has train sounds rather than my dreadful music this time \ud83d\ude09 ).<\/p>\n

I’m also pleased to say that Cross-City South v1.4 now includes a full set of on-train conductor’s announcements<\/strong>, with enormous thanks to voice recording artist Pete Kingwell \u00bb http:\/\/www.petekingwell.com \u00ab<\/a><\/span>. Pete has also recorded a set of alternative Birmingham New Street station announcements<\/strong>, and we agreed that all these sounds could be released into the public domain along with the rest of the Cross-City South v1.4 files once released. Thanks must also go to Paul Sladen (maintainer of the Ubuntu version of openBVE) for intiating this aspect of the project as well. I’m glad to be able to remove another set of copyright files from the route now, while being able to add something new which has been missing from the Cross-City South route for years as well, and an example on-train announcement is included in the video.<\/p>\n

While viewing the 323’s cab, please note that I don’t actually know what the non-driver’s side of the cab looks like in any detail at all, so I’ve just had to use my imagination; if anyone can point out inaccuracies, feel free to tell me about them. Other than that, enjoy. \ud83d\ude42<\/p>\n\n\n\n
\"Horizontal
\nVideo:<\/strong> Demonstration of class 323 3D cab, interior fittings, and Watford Junction to Rugby hi-res (work-in-progress)<\/span><\/p>\n

I strongly recommend viewing this video in full screen due to some night time shots, in which some details might be hard to make out otherwise.<\/p>\n

By the way, yes, I know 323 EMUs don’t run from Watford Junction — that part of the video is just a bit of fun. \ud83d\ude42<\/p>\n


\n<\/span><\/p>\n

<\/embed><\/object><\/p>\n

\u00bb Link to YouTube page (HD – *Best Quality*) \u00ab<\/a>
\n\u00bb Link to YouTube page (High Quality) \u00ab<\/a><\/p>\n

\"Horizontal<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Here’s a 1280×1024 resolution screenshot of the new 3D cab. The framerate here is 25 fps, with 8x anti-aliasing and 16x anisotropic filtering enabled (on a Radeon HD 2600 Pro graphics card). Smooth transparency and anistropic filtering was also enabled in openBVE’s settings as well:<\/p>\n\n\n\n

\n\"openBVE<\/a>
\nopenBVE \/ 3D Cab \/ X-City South v1.4 screenshot–click to enlarge<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\"Horizontal
\n3D Cab Features and Animation<\/span><\/strong><\/p>\n

For the 323’s 3D cab, I’ve opted for a combination of moderately complex 3D geometry combined with photo-realistic textures, some of which were easily adapted from the existing 2D panel images. Developing the new cab wasn’t really more difficult than developing any other animated object, as that is exactly what the cab is — it just took longer as there are more animated parts. The most difficult tasks I found, were probably the gauges and needles, which needed quite a lot of experimentation before the results were right, partly because the 323’s panel is sloped backwards rather than being vertical, meaning that correctly tilting the axis around which the animated needles rotate took a little while.<\/p>\n

As an additional starting point for other train developers, here are the functions I’m using in the panel.animated<\/em> file for the speedometer, main reservoir and brake cylinder needles, amongst other features, which I’m using.<\/p>\n

Note:<\/strong> Some examples include two states, where one specifies an object illuminated by in-cab lighting, and the other specifies a non-emissive version of the object, shown when the power is cut, based on state of the ats31<\/em> plugin variable defined in the 323’s panel2.cfg file (when used with Simon Gathercole\u2019s UKMUt.dll).<\/p>\n\n\n\n
\"Horizontal
\nThe Base 3D Cab<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n

Base 3D Cab Objects:<\/span><\/strong><\/p>\n

[object]
\nstates = 3dcab\\class323_dmso_cab_interior_lights_on.csv, 3dcab\\class323_dmso_cab_interior_lights_off.csv
\nstatefunction = !pluginstate[31]<\/p>\n<\/div>\n

<\/strong>These two objects contain any non-animated portions of the cab, but one is a duplicate with emissive properties disabled, so in-cab lighting can be turned on and off according to the state of plugin variable ats31<\/em> in this case, which simulates the effect of the power being cut, or a cold and dark cab environment.<\/p>\n\n\n\n
\"Horizontal
\nSpeedometer and Brake Gauge<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\nSpeedometer Needle Object (with day\/night textures):<\/span><\/strong><\/p>\n

CreateMeshBuilder
\nAddVertex,-0.003,0.04,0
\nAddVertex,0.003,0.04,0
\nAddVertex,0.003,0.00,0
\nAddVertex,-0.003,0.00,0
\nAddFace,0,1,2,3<\/p>\n

LoadTexture,speedometer_needle.bmp, speedometer_needle_n.bmp
\nSetTextureCoordinates,0, 0, 0
\nSetTextureCoordinates,1, 1, 0
\nSetTextureCoordinates,2, 1, 1
\nSetTextureCoordinates,3, 0, 1
\nSetDecalTransparentColor,0,0,0
\nSetEmissiveColor,200,200,200<\/p>\n

RotateAll,0,1,0,90<\/p>\n<\/div>\n

\"Horizontal<\/p>\n

\nSpeedometer (100 mph):<\/span><\/strong><\/p>\n

[object]
\nstates = 3dcab\\gauges\\speedometer_needle.csv, 3dcab\\gauges\\speedometer_needle_dark.csv
\nstatefunction = !pluginstate[31]
\nposition = -0.5505, 2.232, 11.452
\nrotatexdirection = -1, 0, 0
\nrotatexfunction = -3.678 + abs[speedometer] * 0.0945
\nrotateyfunction = -1.11
\nrotatezfunction = -1.57<\/p>\n<\/div>\n

<\/strong>The gauge background and cover are included as part of the base 3D geometry of the cab itself, not as seperate objects. The value -3.678 in rotatexfunction<\/tt> rotates the needle to 0 mph on this speedometer (adjust for your own gauge as required, using ObjectViewer to check the results). Where the last value (0.0945) is concerned, you can adjust this, initially, in 0.01 increments and test drive your train in openBVE until your speedometer is calibrated correctly (press Ctrl+V multiple times as required in-game, and compare the actual speed with the speed shown on the speedometer). Alternatively, you can temporarily replace the variable speedometer<\/tt> with a value in m\/s (converted from the unit of measurement shown on your speedometer), check the calibration via ObjectViewer, and adjust the last value accordingly. The other rotation commands are there to tilt the axis around which the needle rotates, to match the sloped 323’s panel.<\/p>\n

A similar approach applies to the following needles:<\/p>\n

\nMain Reservoir (range covers 7-8 bar, as per the 2D panel):<\/span><\/strong><\/p>\n

[object]
\nstates = 3dcab\\gauges\\brake_needle.csv, 3dcab\\gauges\\brake_needle_dark.csv
\nstatefunction = !pluginstate[31]
\nposition = -0.741, 2.263, 11.462
\nrotatexdirection = -1, 0, 0
\nrotatexfunction = 1.12 + mainReservoir * 0.0000051
\nrotateyfunction = -1.11
\nrotatezfunction = -1.57<\/p>\n

Brake Cylinder (range covers around 0-3.5 bar, as per the 2D panel)<\/span><\/strong><\/p>\n

[object]
\nstates = 3dcab\\controls\\brake_needle.csv, 3dcab\\controls\\brake_needle_dark.csv
\nstatefunction = !pluginstate[31]
\nposition = -0.731, 2.263, 11.462
\nrotatexdirection = 1, 0, 0
\nrotatexfunction = -1.52 + brakeCylinder * 0.0000053
\nrotateyfunction = -1.11
\nrotatezfunction = -1.57<\/p>\n<\/div>\n\n\n\n
\"Horizontal
\nCombined Traction\/Brake Controller<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The reverser is pretty straightforward, however this is what I’m using for the combined power\/brake handle:<\/p>\n

\nCombined Traction\/Brake Controller:<\/span><\/strong><\/p>\n

[object]
\nstates = 3dcab\\controls\\power_handle.csv, 3dcab\\controls\\power_handle_dark.csv
\nposition = -0.952, 2.0, 11.173
\nstatefunction = !pluginstate[31]
\nrotatexfunction = if[powerNotch >= 1, -0.125 * powerNotch, 0.10 * brakeNotchLinear]
\nrotatexdamping = 20, 0.8
\nrotatezfunction = if[powerNotch >= 1, 0.05, 0]
\nrotatezdamping = 20, 1<\/p>\n<\/div>\n

\"ClassThe rotatexfunction<\/tt> line allows both brake and power notches to be taken into account; adjust the -0.125 value to change the angle of the controller when position P1 or above is chosen, and similarly the value 0.10 for the brake steps. While determining what values to use, you can temporarily replace the above function in rotatexfunction<\/tt> with a simple function in the form of ROTATION_VALUE * x<\/em><\/tt>, where the former determines the degree of rotation, and x<\/em> represents your chosen power\/brake setting (for example, in the case of the class 323, a value of 1 to 4 for position P1-P4, and similarly 1 to 4 for position B1 to B3 and EMG as we’re using brakeNotchLinear<\/tt> here).<\/p>\n

Also, the class 323’s combined traction\/brake controller doesn’t just pivot back and forth; it’s also offset slightly to the left during the P1-P4 steps compared to the B1-B3 steps (you can see this in the screenshot on the left), which is what the rotatezfunction<\/tt> and rotatezdamping<\/tt> commands are for.<\/p>\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Incidentally, you might have noticed that the combined traction\/brake handle appears to be a rather rounded, and smoothly sculpted object — this is achieved with a combination of 3D geometry and a good texture which captured some reflected light, further improved with custom normals<\/a> (as another side note, the spherical object at the end of the horn lever shown in the next section is a pair of simple 2D surfaces arranged in a cruciform fashion; no detailed 3D geometry is needed there). How might one go about creating an object like this power\/brake controller, without a 3D modelling tool? What I do, is apply the idea of the computed axial tomography medical imaging technique (CT scan) to object building; I first create a set of flat, 2D polygons or layers with temporary faces to build the basic framework of the mesh (you can draw this on paper first and number the vertices, if it helps — handy when it comes to defining faces and texture mapping later), then I adjust the vertices of the first layer until the shape looks about right, and then create the next layer and adjust and so-on, and then define final faces of the object and delete the temporary faces, followed by the addition of custom normals and texture mapping:
\n\"Class
\nThis is also the technique I used for creating the AC electric loco roof sections, by the way:
\n\"AC<\/a><\/p>\n\n\n\n
\"Horizontal
\nHorn Lever<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\nHorn Lever:<\/span><\/strong><\/p>\n

[object]
\nstates = 3dcab\\horn_lever.csv, 3dcab\\horn_lever_dark.csv
\nposition = -0.07, 2.06, 11.234
\nstatefunction = !pluginstate[31]
\nrotatexfunction = pluginstate[24] * 0.5
\nrotatexdamping = 30, 0.8
\nrotateyfunction = -0.3<\/p>\n<\/div>\n

<\/strong> The horn lever was straightforward to implement; it’s rotation simply depends on the value of the ats24 <\/em>plugin variable in this case. rotateyfunction = -0.3<\/tt> simply rotates the object so it’s perpendicular to the desk panel it’s attached to.<\/p>\n\n\n\n
\"Horizontal
\nOther indicators<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\nFor any other standard atsi plugin variable with two states (e.g. 0 and 1):<\/span><\/strong><\/p>\n

<\/strong>[object]
\nstates = 3dcab\\indicators\\tpws_isol.csv
\nposition = 0, 0, 0
\nstatefunction = !pluginstate[10]<\/p>\n<\/div>\n

<\/strong>This is simple and works fine, and is also recommended. However, if on a state change, you notice that the newly loaded object appears momentarily untextured, and this bothers you, then you can use the following technique instead…<\/p>\n

\n[object]
\nstates = 3dcab\\controls\\dra.csv
\nposition = 0, 0, 0
\ntextureshiftyfunction = pluginstate[13] * 0.5\n<\/div>\n

\"Horizontal<\/p>\n

\nTexture mapping in dra.csv object:<\/span><\/strong><\/p>\n

CreateMeshBuilder
\nAddVertex,-0.5905,2.0885,11.381
\nAddVertex,-0.5485,2.0885,11.381
\nAddVertex,-0.5485,2.0525,11.365
\nAddVertex,-0.5905,2.0525,11.365
\nAddFace,0,1,2,3<\/p>\n

SetTextureCoordinates,0, 0, 0
\nSetTextureCoordinates,1, 1, 0
\nSetTextureCoordinates,2, 1, 0.5
\nSetTextureCoordinates,3, 0, 0.5
\nSetDecalTransparentColor,0,0,255
\nSetEmissiveColor,255,255,255
\nSetColor,130,130,130
\nSetBlendMode,Additive<\/p>\n<\/div>\n

Here, the illuminated DRA image is placed in the bottom half of the texture, while the top half of the image is transparent. By using a texture shifting function, no state change occurs, so you won’t notice any momentarily untextured surface appearing which can happen when a state is changed and the object hasn’t been loaded previously.<\/p>\n\n\n\n
\"DRA<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

If, for example, your ats subject had 4 states rather than 2 as in the above DRA example (with it’s bitmap split into 4 sections), you could use a value of 0.25 (i.e. 1 \/ 4) in your texture shifting function instead:<\/p>\n\n\n\n
\"Proving<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n
\"Horizontal
\nSimulated Headlight Effects<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

I’m still experimenting with the simulated in-cab headlight effects and some refinements are needed, but here’s what I’ve come up with so far:<\/p>\n

Working Headlight (panel.animated file):<\/span><\/strong><\/p>\n

[object]
\nstates = 3dcab\\ext_headlight_1.csv, 3dcab\\ext_headlight_1a.csv, 3dcab\\ext_headlight_1b.csv
\nposition = 0, 0, 0
\nstatefunction = if[pluginstate[20] > 0, pluginstate[20] – 1, -1]<\/p>\n<\/div>\n

The object code I’m using is like the following:<\/p>\n

\nWorking Headlights (csv object example):<\/span><\/strong><\/p>\n

ext_headlight_1.csv<\/span><\/p>\n

CreateMeshBuilder
\nAddVertex,-1.3, 3.0, 11.67
\nAddVertex,0.6, 3.0, 11.67
\nAddVertex,0.6, 1.5, 11.67
\nAddVertex,-1.3, 1.5, 11.67
\nAddFace,0,1,2,3<\/p>\n

LoadTexture,transparent.png, headlight_interior.png
\nSetTextureCoordinates,0, 0, 0
\nSetTextureCoordinates,1, 1, 0
\nSetTextureCoordinates,2, 1, 1
\nSetTextureCoordinates,3, 0, 1
\nSetBlendMode,Additive
\nSetColor,150,130,100,120<\/p>\n<\/div>\n

The three objects are flat, vertical surfaces which load a simple texture with a sunburst gradient fill, representing a glow (similar to the light_xxxxx.png<\/em> signal glow images included with openBVE’s compatibility signal objects, or the pantograph sparking effects I’ve shown previously). The glow colour in the texture is white, and the SetColor<\/tt> command is used to determine what colour headlight is depicted (a yellowish-white in the example above); this way, only one texture is needed. These objects are positioned just beyond the cab window, and the additive blending mode simulates the effect of illuminating whatever is behind the surface (the track and scenery, in this case). The height of the surface determines whether just the track, or the scenery, appears to be illuminated. The file “transparent.png” is a tiny, completely transparent PNG file loaded as the daytime texture, so the headlight effect is only visible in low light (as it’s loaded as a nighttime texture), or when the .Brightness command is used.<\/p>\n

The states are linked to the proving lights in the cab (ats20<\/em>), and each object has it’s surface repositioned to simulate headlights on the left or right, or centred in the case of the marker lights.<\/p>\n

There is one caveat however; while this works well at night, or when in a tunnel during daytime, the effect doesn’t look so good when passing beneath a short overbridge (i.e. where a low .Brightness value is set over a distance of just a few metres), as the headlight glow becomes visible here, when in reality it wouldn’t. As a compromise, what I’ll probably do in the final release, is reserve the headlight effect for the nighttime headlight configuration only, not the daytime configuration (possible with the UKMUt.dll plugin). You’ll have to decide whether this minor issue is worth it or not.
\n\"Horizontal<\/p>\n

Class 323 Interior<\/strong><\/span><\/p>\n

I thought I’d talk a little about the 323’s interior as well. The interior view features the expected things; i.e. seats and partitions, but I’ve also included working TV screens, working carriage lighting, raindrop effects which run down and streak across the windows at varying speeds (depending on the speed of the train), and ground illumination from the windows and sparking pantograph.<\/p>\n\n\n\n
\"Horizontal
\nWorking TV Screens<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The working TV screens use simple texture shifting and translation functions — for the left screen with the car and rolling news ticker, there’s nothing I haven’t described before, apart from applying the functions to a very different set of meshes. Where the static effect is concerned, this is created by using two surfaces with a small texture containing a patchwork of black and white pixels; one of the objects has the texture reversed vertically and horizontally. One object is positioned slightly in front of the other, and both have alpha values set via the SetColor<\/tt> command to soften the appearance of the end result. These objects then have their textures shifted via the same function:<\/p>\n

\nTV Screen Static Effect (Object 1):<\/span><\/strong><\/p>\n

CreateMeshBuilder
\nAddVertex,0.46, 3.492, 3.597
\nAddVertex,0.765, 3.492, 3.597
\nAddVertex,0.765, 3.273, 3.597
\nAddVertex,0.46, 3.273, 3.597
\nAddFace,0,1,2,3<\/p>\n

LoadTexture,Class323_TV_Texture_2.png
\nSetTextureCoordinates,0, 2, 0
\nSetTextureCoordinates,1, -0.001, 0
\nSetTextureCoordinates,2, -0.001, 2
\nSetTextureCoordinates,3, 2, 2
\nSetColor,0,0,0,180
\nSetEmissiveColor,255,255,255<\/p>\n<\/div>\n

\"Horizontal<\/p>\n

\nTV Screen Static Effect (Object 2):<\/span><\/strong><\/p>\n

AddVertex,0.46, 3.492, 3.595
\nAddVertex,0.765, 3.492, 3.595
\nAddVertex,0.765, 3.273, 3.595
\nAddVertex,0.46, 3.273, 3.595
\nAddFace,0,1,2,3<\/p>\n

LoadTexture,Class323_TV_Texture_2.png
\nSetTextureCoordinates,0, 2, 0
\nSetTextureCoordinates,1, 2, 2
\nSetTextureCoordinates,2, -0.001, 2
\nSetTextureCoordinates,3, -0.001, 0
\nSetColor,0,0,0,180
\nSetEmissiveColor,255,255,255<\/p>\n<\/div>\n

\"Horizontal<\/p>\n

\nTV Screen Static Effect (Animation Function):<\/span><\/strong><\/p>\n

[object]
\nstates = ..\\Class323_TV_2.csv, ..\\Class323_TV_2a.csv
\nposition = 0, 0, 0
\nstatefunction = if[pluginstate[31] == 0 & pluginstate[33] == 0, -1, value == 0]
\ntextureshiftxfunction = 2 * time
\nrefreshrate = 0.01<\/p>\n<\/div>\n

The pluginstate[i]<\/tt> variables are there so that the TVs are only switched on when there’s power, and stay on when passing though a neutral section (ats31 is the Line Volts indicator, and ats33 the Vacuum Circuit Breaker indicator). The refreshrate = 0.01<\/tt> line just adds a slight degree of flickering to the screen.<\/p>\n\n\n\n
\"Horizontal
\nWindow raindrop effects<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The raindrop effects also deserve a little more explanation. These are comprised of two surfaces, the first of which has ordinary raindrops similar to what you’ve seen in BVE 4 cabs, except here, the surface simply has one tiled, transparent texture containing multiple raindrops and the texture is slowly shifted. The second surface, loads a texture depicting several streaking rain drops, and the speed of the streaking is linked to the speed of the train, although they still move slowly down the window when the train is stationary. What I did differently, was to make the surface irregularly shaped, so the raindrops appear to change direction as they travel across the window due to turbulence or inteference:<\/p>\n\n\n\n
\"Raindrop<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\nRaindrop effect animation code:<\/span><\/strong><\/p>\n

[Object]
\nposition = 0, 0, 0
\nstates = Class323_DMSO_1_RainDrops_1.csv
\nstatefunction = !pluginstate[200]
\ntextureshiftyfunction = -0.1 * time
\ntextureshiftxdirection = 0, 1
\ntextureshiftxfunction = value – delta * speed \/ 60
\nrefreshrate = 0.01<\/p>\n<\/div>\n

ats200<\/tt> is one of the raindrops you’re familiar with from the 2D BVE 4 cabs…<\/p>\n\n\n\n
\"Horizontal
\nPantograph spark and ground lighting effect<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The pantograph sparking and ground illumination effect is a simple additively blended glow effect, which will appear mostly briefly at various times during a journey, but not continuously and not necessarily frequently. When seen for the first time, it might seem as though the effect appears at random, but actually the times at which you’ll see sparking are based on the speed of the train. This is acheived via the following function:<\/p>\n

\nSparking effect:<\/span><\/strong><\/p>\n

[Object]
\nstates = Class323_Spark_1.csv
\nposition = 0, 0, 0
\nstatefunction = if[mod[speed, 3] > 2.9, value == 0, -1]
\nrefreshrate = 0.03<\/p>\n<\/div>\n\n\n\n
\"Horizontal
\nFlashing Tail Light<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

In terms of visual effect, the tail light is implemented just like the signal aspects. The animation code I’m using to achieve a short blink followed by a longer period of extinguishment is as follows:<\/p>\n

\nFlashing Tail Lamp Animation:<\/span><\/strong><\/p>\n

[Object]
\nStates = TailLamp_1a.csv
\nPosition = 0, 0, 0
\nStateFunction = if[mod[time, 0.55] > 0.08, -1, 0]<\/p>\n<\/div>\n\n\n\n
\"Horizontal
\nSignal Ground Lighting<\/strong>
\n\"Horizontal
\n\"openBVE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

These effects are really easy — the objects are just like the headlight objects mentioned previously, except these extend out behind the signal and are animated objects loaded via .SigF commands instead. The simple animation function I’m now using is as follows:<\/p>\n

\nSignal ground lighting animation function (assumes .Section 0;2;3;4 commands and 4 aspect signals):<\/strong><\/p>\n

[Object]
\nPosition = 0, 0, 0
\nStates = Sig_GroundLight_R.csv, Sig_GroundLight_Y.csv, Sig_GroundLight_Y.csv, Sig_GroundLight_G.csv
\nStateFunction = if[section > 0, section – 1, 0]<\/p>\n<\/div>\n

Incidentally, I’ve now adopted more or less the same technique developed by michelle for openBVE’s compatibility signal objects where my own signal aspect\/lens and glow effects are concerned, as it’s obvious that a lot of care went into these effects, and they look superb when applied to my own signal objects with the lens hoods as well (see the video…).
\n\"Horizontal<\/p>\n

Updated Pantograph Animation Functions<\/strong><\/span><\/p>\n

Lastly, I’ve updated my old Animated Exterior Car Objects blog entry<\/a> to include some updated unctions which resolve a problem with the code which I hadn’t considered previously. Bascially, the code I used meant that the pantograph animation speed was dependent on the framerate on the user’s computer, which is obviously no good — if slow framerates were encountered, the animation would proceed very slowly, while if high framerates were experienced, the animation speed would be too high. By incorporating the delta variable and a factor into the functions, this problem is solved. Actually this should have occured to me, because I observed this behaviour when I was experimenting with the wheel rotation initially… D’oh. Thanks michelle !<\/p>\n

I also thought you might like to see a high resolution image of Cross-City South v1.4 and the new high detail class 323; in this screenshot, I’m running openBVE fullscreen at a resolution of 1280×1024, with 8x anti-aliasing and 16x anisotropic filtering enabled (on a Radeon HD 2600 Pro graphics card). Bilinear interpolation was enabled in openBVE’s settings, with the Transparency mode set to Sharp. I was getting around 16-19 fps at the time; the framerates in the next version of openBVE will hopefully be a little higher due to performance optimisations where animated object normals are concerned, although this gain may be offset by the addition of more animated scenery objects to the route:<\/div>\n","protected":false},"excerpt":{"rendered":"

openBVE v1.1.1.0 (Development Branch), 3D cabs, and other stuff… The first release (v1.1.0.0) in the development branch of openBVE was made available a few days ago, and now v1.1.1.0 has subsequently been released — the development branch includes support for full 3D cabs with animated objects, and mouse controlled camera rotation. v1.1.1.0 also introduces driver’s […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[6,7,8,9,11,15,20,21],"class_list":["post-885","post","type-post","status-publish","format-standard","hentry","category-openbve","tag-animated-objects","tag-artwork","tag-cross-city-south","tag-functions","tag-openbve","tag-screenshots","tag-videos","tag-watford-jn-to-rugby"],"_links":{"self":[{"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/posts\/885","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/comments?post=885"}],"version-history":[{"count":0,"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/posts\/885\/revisions"}],"wp:attachment":[{"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/media?parent=885"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/categories?post=885"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/railsimroutes.net\/blog\/wp-json\/wp\/v2\/tags?post=885"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}