Home LittleBigPlanet 1 - PSP - Tearaway -Run Sackboy Run LittleBigPlanet 1 [LBP1] Tutorials [Archive]
#1
Advanced Chrome Glitch Techniques
Archive: 7 posts
Ever since the chrome glitch (https://lbpcentral.lbp-hub.com/index.php?t=36483-Very-Rare-chrome-glitch) was discovered, I've been fascinated by it. I've discovered several new techniques using it and I'd like to share them with you: How to delete chrome glitch objects/turn them back to normal This unfortunately only works for chrome glitch objects that contain connectors (winch, string, rod, etc.). 1. Select the connector. The entire object will "snap back" to normal. It will be unselectable though, and still be static like Dark Matter. 2. Glue another object to the "ex-chrome" object and select it. It will now be selectable/deletable. How to make chrome glitch objects mobile but still intangible 1. Create the object you'd like to apply this property to, and attach it with a connector to a block of material. 2. Capture the whole thing and chrome glitch it. 3. Select the end of the connector that's attached to the material. The material will become solid but the other object will stay chrome glitched. Unfortunately, it's still static. 4. Get out any material brush and cut away from the material block (Make sure you don't cut away from the part the connector is attached to). The chrome-glitched object will lose its static property and behave like a normal object, but still be intangible and transparent! How to bolt chrome glitch objects to normal objects This is pretty much an extension of the last one. 1. Create the object you want to do this to. Bolt it to another material of your choice. Now attach that material with a connector to a block of Dark Matter. 2. Capture and chrome glitch the whole thing. 3. Select both ends of the connector, one at a time, but not the connector itself. If you did it right the first object will be the only one still chrome-glitched. 4. Use the material brush to cut away from the DM block. 5. Select the block of DM and delete it by holding down the Triangle button. This will also get rid of the connector. 6. The chrome glitch object that's bolted on will now behave like a normal object but still be intangible and transparent! Do not select the object it's bolted to however, or it will snap back to normal. How to get chrome-glitched "decal objects" on normal objects This one is kind of useless, but I decided to include it anyway. (What I call "decal objects" are objects like magnetic keys, magic mouths, sound objects, etc.) 1. Get out the object of your choice, with the decal objects you want to do this to attached to it. 2. Create a block of Dark Matter, and attach it with a connector to the first object. 3. Capture and chrome glitch the whole thing. 4. Select both ends of the connector, one at a time, but not the connector itself. If you did it right the object will now be normal, but the decal objects on it will still be transparent. 5. Use the material brush to cut away from the block of DM. 6. (Optional) Select the block of DM and delete it by holding down the Triangle button. This will also get rid of the connector. Be careful not to select the object they're attached to, or they'll all snap back to normal. Notes: - Mobile chrome glitch objects still weigh as much as normal objects. - All chrome glitch objects can still be destroyed through the mortisphere (outer level boundaries). - In LBP1, chrome glitch objects attached to normal objects can still be captured, but only by their original creator. - In LBP2, chrome glitch objects attached to normal objects cannot be captured by the Capture tool, but they can be captured by an emitter's built-in capture function (similarly to Dead material) - Placing them directly from My Objects causes the chrome effects to go away, but they can be placed properly by emitting them. - Mobile chrome glitch objects can still be broken if enough force is exerted on them (such as an extremely fast motor bolt) - Chrome glitch objects that are glued together will become unglued if their static property is removed. - Chrome glitch versions of objects with special effects (such as enhancements or score bubbles) will still work normally in LBP1. Not so much in LBP2, though... - If an object with a finite lifetime is chrome glitched, its lifetime will become infinite again, even if it was killed with a creature brain. - In LBP2, if a chrome glitch object is spawned with the "fade" animation, it will not be transparent and will look exactly like a normal object. There you go! Hopefully this will give a lot more versatility and usefulness to the chrome glitch! | 2010-12-17 07:30:00 Author: Blue Helmet Posts: 306 |
Huh i was searching for a solution for that!THX ! | 2010-12-18 00:10:00 Author: robotixpro Posts: 354 |
Think I might have discovered something else new. As I was editing my level yesterday, all the chrome glitch objects spontaneously lost their "static" properties and became subject to gravity again. In retrospect, the only thing out of the ordinary that I'd done was using the compression tool. Could this mean that the compression tool can also make chrome glitch objects non-static...? EDIT: Apparently it doesn't. Meaning all those objects somehow lost their static property by themselves... | 2011-01-04 20:29:00 Author: Blue Helmet Posts: 306 |
wow, when creator B showed me it, we experimented alot, we figured out how to make checkpoints and thermoless levels, but you took it the next step, and you found out very very usefull things, so definately kudos! | 2011-01-12 16:12:00 Author: dragonights Posts: 209 |
Okay, after several attempts I can sadly confirm that the chrome glitch has been patched in LBP2. It's been made impossible to either create chrome glitch objects, or capture ones that already exist in imported levels. However, it is still possible to use the emitter method to place already-captured ones. EDIT: Also, chrome glitch score/prize bubbles, which were collectible in LBP1, are no longer collectible in LBP2... EDIT 2: Wow, I completely forgot about this method (https://lbpcentral.lbp-hub.com/index.php?t=38197-Chrome-glitch-methods). I'll have to see if it still works in LBP2. EDIT 3: Just tried it out and yes, that method still works! That means that it is still possible to make chrome glitch objects in LBP2!!! | 2011-01-24 19:58:00 Author: Blue Helmet Posts: 306 |
ahh sweet i <3 this method: 2. Glue another object to the "ex-chrome" object and select it. It will now be selectable/deletable. | 2011-01-28 06:23:00 Author: silversade Posts: 15 |
Okay, after several attempts I can sadly confirm that the chrome glitch has been patched in LBP2. It's been made impossible to either create chrome glitch objects, or capture ones that already exist in imported levels. However, it is still possible to use the emitter method to place already-captured ones. EDIT: Also, chrome glitch score/prize bubbles, which were collectible in LBP1, are no longer collectible in LBP2... EDIT 2: Wow, I completely forgot about this method (https://lbpcentral.lbp-hub.com/index.php?t=38197-Chrome-glitch-methods). I'll have to see if it still works in LBP2. EDIT 3: Just tried it out and yes, that method still works! That means that it is still possible to make chrome glitch objects in LBP2!!! I can confirm that this does indeed still work after the 1.02 update. I actually discovered this glitched a few weeks ago with my friend playing online but couldn't figure out how to recreate it. She was placing a sackbot, and before she could place it the game diverged and this exact glitch happened. | 2011-03-18 03:16:00 Author: Unknown User |
LBPCentral Archive Statistics
Posts: 1077139
Threads: 69970
Members: 9661
Archive-Date: 2019-01-19
Datenschutz
Aus dem Archiv wurden alle persönlichen Daten wie Name, Anschrift, Email etc. - aber auch sämtliche Inhalte wie z.B. persönliche Nachrichten - entfernt.
Die Nutzung dieser Webseite erfolgt ohne Speicherung personenbezogener Daten. Es werden keinerlei Cookies, Logs, 3rd-Party-Plugins etc. verwendet.
Die Nutzung dieser Webseite erfolgt ohne Speicherung personenbezogener Daten. Es werden keinerlei Cookies, Logs, 3rd-Party-Plugins etc. verwendet.