View Full Version : Possible Glitch. Extremely Lame
03-27-2011, 03:08 PM
I've spent 50+ hours developing a flawless 16 character passcode input system that is not a game detractor and poses minimum annoyance for the player as well. The amount of passcodes I can make are endless. The passcode allow an alternate method to transferring data through a level link without using score.
Now the apparent bug, while my system is unbreakable due to extensive debugging, apparently I can only use it as I build it. If I capture it or copy it, deleting the original or not, it completely messes up. So if I want to experiment with it, I have to modify the original instead of modifying a copy. I've also tried copying little bits at a time. Still doesn't work. It's not half as complicated as some of the logic I have seen used in levels. The only workaround I've found is copying the entire level to a new crator in order to create one copy that works. So, not exactly sure what's happening, but if anyone feels they can help me, please add me as friend so I can demonstrate.
03-28-2011, 04:50 AM
As I watched you build it, I noticed that you simply copied everything from existing places, which isn't a problem at first, but re-copying copied objects tends to glitch some logic. One way you can fix your system is to create the original without copying anything that has logic on it. For your system, it would take a while, so I don't recommend it, but it helps keep creations glitch-free. The only other way I could think to fix this is to wire everything instead of having everything wireless, which would make a huge mess for your system, but it may hold some greater reliability. You can ask me to help with either if you want ;)
03-28-2011, 04:59 AM
This seems to be related.
Sometimes when I copy logic pieces, they will obtain bizarre properties, though this rarely occurs. Sensors are the main issue. I've had min ranges greater than max range, angles that are not aligned with the direction of the sensor (eg: 90 degrees offset, so I have to turn the piece 90 degrees to correct it), and failure to use the correct label (displayed the correct one, but didn't respond to it).
Again, these have only occurred very few times, but they could be an issue you are facing?
03-28-2011, 05:30 AM
There's not a whole lot we can tell you without seeing the circuit, and even then we might not be able to do much--logic a lot of times only makes sense to the person who built it. As Stag pointed out, sometimes sensors get messed up, though I doubt you use many in your system since it's more likely that you're using the score to encode/decode the data. Another issue is the order in which signals propagate: sometimes when you build the chip things get out of order and then get corrected when it's copied. I say corrected because they go back to the proper behavior according to the game engine, but if your system was dependent on the wrong order, then it stops working. I built an emotion chip (control's sackbot emotions) that worked exactly like the default sackboy emotions and it worked fine, but when I copied it, it broke and I had to add .1s delays to some of the signals to fix it.
The only thing I can really suggest is to organize your chip the best you can so that you can see what the signals are doing and maybe add in some sort of indicators (I like using positional sequencers to test analog signals, for example) to try to see where your signals are getting messed up. If you can't figure it out, maybe you'll at least be able to get s'more specific information that we can examine and see if we have any suggestions.
03-28-2011, 06:27 AM
Well, I do thank you for all your input. Shuriken, I may ask for your help later in redoing the whole piece...gonna be really annoying...especially the tags and sensors. ugh lol.
@Sehven: I am actually very organised with my logic, everything is usually always labeled, controllinators, microchips, sensors and tags, etc. I try to keep my stuff very neat and organised. As far as score sensors, I don't use them at all. I use tags and tag sensors to do my password. I do have a lot of them, but only one is ever active at a time, due to the way it is set up. I'm not exactly sure how to show my problem as you can really only see it demonstrated in-game. It's baffled all of my friends, so not sure whats going on. But a complete stranger could look at my logic and after 5-10 minutes of examining it, they will understand how it works. You're more than welcome to come see yourself, cause a solution would be a great thing lol. Again, thanks everyone for your input.
03-28-2011, 04:58 PM
No problem, I'm about 95% finished with my new hover-tank anyways. I just gotta get my targetting display to work when the tank's upside-down now & fix my glitchy dual turrets.
03-28-2011, 05:33 PM
Sorry, I was tired last night. I read your post about using a password system but while I was mulling it over in my brain, for some reason I started thinking you were talking about a score-based encoding system for transferring data to sub-levels. My bad. Sorry, but aside from sensors glitching and race conditions, I don't know much about microchips glitches.
I used to be a cable guy and I was always really good at chasing down signal problems (I had fewer repeat trouble calls than anybody else out of our office). It was always a matter of divide and conquer. If there was a problem with the signal at the tv or modem, I would go outside to where the signal came into the house and check it there. If it was bad there, I knew it was either the main line or the cable coming from the main line to the house; if it was good there, I knew it was somewhere in the house so I'd move on to the main splitter in the house and so on. I use the same principles when debugging lbp logic--I look at the signal at various stages to see if it's doing what it's supposed to be doing (if necessary, you can compare it side by side with the original chip). If it's good there, I move down the line and check again; if it's bad, I move up the line toward the beginning of the chip and check there. That's not very specific and it's possible that you need to have a knack for it or something, or that your particular problem is a fluke, but that's the best I can come up with.
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.