PDA

View Full Version : Using one memorizer to record multiple events



Taffey
01-17-2013, 05:43 PM
I have no doubt this question has been answered before (likely for LBP2), but I can't quite seem to find the exact answer I'm looking for.

My little project (http://www.lbpcentral.com/forums/showthread.php?76271-A-level-type-thing-I-m-working-on) I'm working on has multiple cutscenes - chapters if you like - and I would really like to add in a skip-to-scene option for people who want to replay the level but may not want to sit through every cutscene or gameplay sequence.

I've already worked out exactly how I want to do this, and it's pretty straightforward. Essentially, every time you complete a "chapter", a memorizer records the event and enables that particular "skip to chapter" dialog the next time you play the level. Easy enough. The problem I am running into is that I will need to use 10 or 15 memorizer labels to accomplish this, and that seems a bit excessive... Still, it may be the simplest and easiest way to do it. I have 50 labels to work with afterall, so it's not like I'm going to run out anytime soon.

Here's what I'm thinking as my workaround. When you complete chapter 1, the memorizer records a value of 10% signal strength (let's say there are 10 chapters). When you complete chapter 2, the memorizer is updated with a value of 20%, and so on. It's simple enough to compare the memorizer's existing value to what it wants to be updated with and use the larger value.

This is where I get kind of stuck. So I have a memorizer with some particular signal strength, say 70%, so now what do I do with it? What is the best way to detect and react in an at least scenario? I can think of a few caveman approaches that seem very clumsy... For example, if I want to detect that a memorizer has at least 70% signal, I multiply the signal by 1.43, which will give me a value of >%100 if the condition is true and <%100 if the condition is false. That just seems kind of meh. I could also use a piston set to positional and have magnetic keys detect tags but geez, that is VERY low tech.


tl;dr - What's the best way to set up logic to react to a signal strength of at least a specific value?

evret
01-18-2013, 07:29 AM
you can simply increase the number of ports on a single memoriser (can go up to 32) to suit your needs, that way you should only need one label

Shade_seeker
01-18-2013, 09:20 AM
Sorry mate, saw your twitter post last night, but was too wrapped up in my level to help (though by the time I saw your post it had already been answered)
Had a quick play around this morning, published it and set it copyable, should be what you are lookin for ( http://vita.lbp.me/v/-jpfw )

So, the sequencer is in directional, so the higher the input (via the batteries) the more the bar travels along from left to right. I set it up with just three, if you want more then just expand all the logic. I hope it all makes sense, message me if you are having trouble:)

Taffey
01-18-2013, 05:11 PM
Thanks guys! I have it figured out now I think.




you can simply increase the number of ports on a single memoriser (can go up to 32) to suit your needs, that way you should only need one labelThis is exactly what I decided to end up doing. I hadn't even really considered using multiple ports. I was stuck on using a single output to distinguish multiple events - this was mostly due to the way I was capturing level progress. I changed my progress capture method and there you go, easy solution.




Sorry mate, saw your twitter post last night, but was too wrapped up in my level to help (though by the time I saw your post it had already been answered)
Had a quick play around this morning, published it and set it copyable, should be what you are lookin for ( http://vita.lbp.me/v/-jpfw )

So, the sequencer is in directional, so the higher the input (via the batteries) the more the bar travels along from left to right. I set it up with just three, if you want more then just expand all the logic. I hope it all makes sense, message me if you are having trouble:)Ah, perfect - I'll take a look! I am probably going to need to do something like this to try and cut down on my tag labels, so this will actually be very useful.

Thanks! 8)