Leaderboard

# ------------------------------------------------- # Sparky s***s himself and runs away # As all his friends are killed in a horrible accident # This is why kids shouldn't pilot rockets...wankers # -------------------------------------------------

Map Download Objects Download (like the collectible star) Pictures: (yes the t-rex is orange) T-rex says "hi"

Blender scene finished, obviously it won't look like a AAA title but I didn't want to spend more than a few hours on it. I'll work on the car next, thank you Xiron for uploading those files!

Should you go through with the remake, can you make the waypoints/collectibles coordinates, as well as the mission timer in a .txt file or something of the like so we can easily customize the routes and such? I'd imagine a hotkey to toggle coordinate display on/off in game would be needed for this to work at all (the display would be in off state by default). Here is the music sections extracted: http://www.mediafire.com/download/y0synpmqp0nh3d4/LEGO_Supersonic_RC__Music.zip As well as some stereo mix recorded sfx: http://oresome.rockraidersunited.com/download/440 This here is the main menu buttons and splashes extracted: http://oresome.rockraidersunited.com/download/441 And here is the ripped objects, car included: http://oresome.rockraidersunited.com/download/442

*ahem*

"Hello again Rock Raider! Another teleport malfunction has occurred, this time affecting the quality of the previously sent Desktop Backgrounds! Thankfully, we've been able to recover in time and we have our new poster pack available for download, so download away Rock Raiders". With the major issue of lighting fixed (and the not-so-major issue regarding the Raiders' belly-button high belt), I'm happy to re-release the renders at a higher quality than before. So, ladies and gentlemen, once again download away and have a lovely Christmas holiday!! DOWNLOAD HERE - http://oresome.rockraidersunited.com/download/443

Dude. Hi. It's me, the guy who loves Templar and knows everything about them. It is my pleasure to deliver to you this forbidden knowledge: they made Supersonic RC. They did most/all the Racers web games up til they stopped working with lego after 2004.

Can't argue with you there haha. This project started out with a far smaller scope than it has now, and while I've done a bit of cleaning up in the main module in recent times, the Raider class and Task system could really use a complete overhaul at some point down the line. Thanks, I'm glad you like it so far! I actually have just about finished implementing the ability for the user to select and place buildings, but a few bugs have popped up that I don't have time to fix right now, so the building update most likely won't be released until after my finals are over. Still, with the recent additions (especially level objectives, scoring, and properly handling loading and switching between levels) we're closer than ever to being able to play through the game in full

I love the Rock Raiders intro, and basically just wanted to try marrying the extra footage of the extended version with the full soundtrack and voices of the release version. Obviously the result isn't perfect, but it isn't quite as jarring as I feared it might be. It's those scenes with the computer screens that they only cut seconds from that get hard to align the sound right with. Also that whole extra scene at the end with Docs and Jet feels unusually quiet.

-Cirevam

Not sure whose job it'd be to correct this, but whoever made this raider model seems to have misinterpreted the texture/original game model. The yellow and black belt is supposed to be printed on the hips, not crammed onto the torso: Compare with, say, the game's loading screen: Or the in-game model - they did the hips and torso as one segment of the model as a polygon saving measure/as there's no reasons to separate them for animation purposes in-game (they also skipped over the "prick", like Alpha Team did later, haha): Side note - there's a lot of variation in the exact details of the torso printing between the game, physical minifigures, books, etc. I imagine it's likely more remnants of non-finalized designs that never got updated, much like the old prototype set designs in the cutscenes. There's also the matter of the minifigs in the game sometimes having leg printing while the real minifigs have none.

Posting rhymes and memes, when suddenly within a second of each other:

https://www.flickr.com/photos/127525305@N02/31473807825/in/photostream/ EDIT: oh, hah, this is the same builder as the ones Dazz posted right above me

And everyone died because of it.

Hi there, I said I would analyze the (available) code to Lego Rock Raiders and see what I can do with it and today I have come to a verdict. I will be able to reconstruct the game engine with the data I have available and the insights created by just looking at the overall configuration of RR and the game mechanics. It won't be easy nor will it be a swift task but it can be done and it will be done. One of my work projects has been postponed til 2017 and the other one is almost done so I feel like I can start on Rock Raiders Reloaded come next week and below is what I will start working on and what I will be planning to do for now with the project. When I start I will be working on: - The base engine (camera controls, HUD, resource control) - Starter elements (Tool Station, Rock Raider, Solid Rock, Dirt, Drills and Shovels) - The start of the Rock Raider AI system (I noticed how bare bone it actually is in the original game and will improve quite a bit) - Basic map design. - Keeping everybody up-to-date with what is going on. What I am planning to do with the project itself: - Recreate the Rock Raiders experience the best I can. - Improve AI for everything. - Make modding a lot easier on the new platform. - Fix a few things that were broken/glitched in the base game (Ore Refinery using more ore than it needs because of zealous Rock Raiders; Trucks dumping more resources than a site needs;) - Redo the way that drilling and using lasers on walls works by giving the walls HP instead of the system that RR used. - Change the Laser Towers into base defense structures which engage enemies in their range when a red alert is active and maybe nerf their EC usage or just remove that altogether. - Create a way of patching that makes sure you don't have to download the whole project every time there's an update. What I am planning for when the project is stable and has what it needs: - Keep improving the project. - Create a multiplayer mode (co-op for now, PvP in whatever form will require some more thought beforehand). - Work on a more complex sequel to Rock Raiders with more resources, buildings, vehicles and a ton more. Let me know what you guys think so far and I'm curious for your opinions and ideas.

This could be interesting! LRR needs a remade engine... the original is too unpleasant and buggy to get working on newer PCs, and we've pushed it to its limits with what little modding it can support. Hopefully with the Unity engine and some of the RRU community assisting, yours will have a better chance of surviving than previous attempts Good luck! Compatibility with the old engine's data files would be nice, but on the other hand, LRR's file formats are unpleasant to deal with. The lightwave meshes can't be made or read correctly by most 3D modelling tools. WADs are useless. The Lego.cfg is huge and jumbled - better to have 1 file per vehicle/building/level/etc. And the map/script files, while fun to decode, really don't need to be in a dense binary format split up into multiple parts. It'd probably be easier and more fun to rebuild the engine the way you'd like it, and just ignore how the old one worked internally. It was a good game, but not a good engine Do you plan on using git or something like that for community contributions, once it's ready for initial release?

Ah yes, that second one is much better. I can actually see things now!

Righto, I've modified the brightness of most lights (especially the Chrome Crusher's, I felt those were unnecessarily blinding), and I want people's opinion; does it look better (or more "readable") now? ORIGINAL: FIXED:

Nice job, thank you for taking the time to do this! I've brought it into Blender and started re-texturing it into a PBR workflow, using much higher resolution textures. It shouldn't take long to finish, most of the textures are done and I just have to assign the new materials to all the objects. The images are noisy because I used a low number of samples. When it's finished, would anyone be interested in me loading it into Unreal Engine? Perhaps if a model can be made of the Supersonic RC in LDD or preferably LDraw, I could use that to make a simple racer game.

Too high a speed and LRR's minimap tracker useless thing will lose sight of it, warp to it, slowly lose sight of it again, warp to it, slowly lose sight of it again, etc etc etc.. Bonus points for PathCoef = 10 Why such bright colours? It's slightly blinding...

Not to be confused with Mech. I won't be uploading music too regularly in the next few months, even, unfortunately. I'm quite busy with school, the soundtrack I'm working on, games... In other words I won't have time to make music for YouTube and y'all in general. Sorry!

Wow, there are the skilled people. Thank you. Cool, I do not know that tool, yet. Maybe I should have a closer look! Indeed! The bricks themselves does not have the studs. Here you can see the part 6564 in the LO version, in the HI version, the bounding box with meta data (I added the studs) and the new HD version (gray is the 'unassign' material, green is the 'nub' material). The bounding box (at least I call it so) defines in a matrix (here 2 x 3) the top and the bottom height of the box and if there is a stud (value >= 128). It is defined in the k_2c section. For the example piece: 131 128 // stud in height 3; (under) stud in height 0 131 128 // stud in height 3; (under) stud in height 0 131 128 // stud in height 3; (under) stud in height 0 131 128 // stud in height 3; (under) stud in height 0 3 64 // no stud but heigt 3; no idea in height 0 3 64 // no stud but heigt 3; no idea in height 0 I can imagine that if a stud meets a understud, it will disappear. Since I did not change the k_2c data, also the old studs appear in the garage. When they are hidden by a new stud you can't see them but they are there. That will be the polygons that got removed. In the races the stud metadata (from k_2c) is ignored. There the material (nub) will be used. So I had to add the studs to the meshes. I do not understand that. The hex value vor (signed int) 2500 is either 0xC4090000 or 0x000009C4?

The names are L239901 and L239902. s00003 is the treasure chest with an 1x4 plate (I think) S00007 is the camera S00014 is the scorpion s00017 is the crossbow s00021 is the I think pirate flag from CR s00022 or s00023 could be the headlights s00029 is the parrot s243200 is an assembly of two 1x2 plates and 2432 Tile, Modified 1 x 2 with Handle s243201 is the rear spoiler sa0010 and sa0011 are two schields (with support); sshield1 and sshield1 are some special shields *CHAS are the chassis (e.g. BBCHAS0, BVBCHA0, DACHAS0, etc.) salndsh and salnds2 are the alien antennas saxe and saxe2 are the long knight axes spear is the small spear spizza will be the pizza :-) sprtgun and sprtgun2 are the guns at the side of a brick sRRpipe and sRRpipe are the pipes from RR car and so on. I will try to create an overview. But at first I will have to do a little more research.