Okay that's double weird.Lunatic Quark wrote:It does the same thing only delayed by 0.2 seconds, there are also no other events in my level currently except the default Level Start and P-Switch events which do nothing...
Have a look in the cinematX code. There is a setting in there called "shouldDespawn". Copy the code used when that's set to false. There's a memory access that forces NPCs not to despawn.Lunatic Quark wrote:Found a way to force it to work with LunaLua, only problem is it despawns if it goes off screen, which is what I was hoping to avoid with the moving layers method to begin with. I'll play around with it later and see if I can find a solution.
That sounds incredibly useful. I'll give it a look after sleep.Hoeloe wrote:Have a look in the cinematX code. There is a setting in there called "shouldDespawn". Copy the code used when that's set to false. There's a memory access that forces NPCs not to despawn.Lunatic Quark wrote:Found a way to force it to work with LunaLua, only problem is it despawns if it goes off screen, which is what I was hoping to avoid with the moving layers method to begin with. I'll play around with it later and see if I can find a solution.
Essentially, all SMBX NPCs have a counter (I believe it starts at 180, which is approximately 3 seconds), which starts decreasing when they are offscreen. When it hits 0, the NPC despawns. To stop them despawning, you just need to set that counter to something non-zero (and greater than 1 to be safe) every frame, so it never reaches 0.Lunatic Quark wrote: That sounds incredibly useful. I'll give it a look after sleep.
Code: Select all
cinematX = loadSharedAPI("cinematX")
Let's see... that line number would mean you're running cinematX 0.0.6nivomi wrote:I just tried importing CinematX and it's crashing in a really exciting and incomprehensible way.
Code: Select all
1185: -- Get the substring between the first and last characters
1186: local checkStringA = string.sub (msgStr, 2, string.len(msgStr)-1)
1187: -- Get JUST the first and last characters
1188: local checkStringB = string.gsub (msgStr, checkStringA, "")
That fixed it. Thanks a bunch!Rednaxela wrote: As a workaround, remove the "[" from your NPC's message I guess.
That looks like an oversight in cinematX. I'll look into it with Rocky when he gets back to working on it.nivomi wrote:That fixed it. Thanks a bunch!Rednaxela wrote: As a workaround, remove the "[" from your NPC's message I guess.
I have to say, working primarily in the PGE editor and LunaLua streamlined the whole experience hugely. The only events and layers I have in my level were those necessary to access Lua. All of the actual control logic and movement was done in Lua, and it made everything a lot easier.Robomorons wrote:Trust me, you're not missing much. When I finally got done with the abomination that was the SMBX engine-based level it was less "Oh, my labor of love finally paid off" and more "Christ! Thank fuck it's over! God!"
Approximately 16,000.Ometeotl wrote:So what's the block limit again?
It's a SMB3 Level, Except Way More Delightful
Apparently 8000 is the limit on background objects. That might be the reason.Ometeotl wrote:Oh good, I was thinking 8000 for some reason.
Those limits are often a few thousand out. I'm not sure why, but the limits are all a lot lower than the SMBX debugger reports.Rednaxela wrote:Apparently 8000 is the limit on background objects. That might be the reason.Ometeotl wrote:Oh good, I was thinking 8000 for some reason.
(You can see that from the SMBX editor in View->Debugger)
I'm rather certain that 5000 for NPCs that it reports is correct, at least for runtime spawning. The others I don't know about.Hoeloe wrote:Those limits are often a few thousand out. I'm not sure why, but the limits are all a lot lower than the SMBX debugger reports.Rednaxela wrote:Apparently 8000 is the limit on background objects. That might be the reason.Ometeotl wrote:Oh good, I was thinking 8000 for some reason.
(You can see that from the SMBX editor in View->Debugger)
I believe the hard limits are as they claim, but crashes and other errors begin to occur long before they're reached. That said, I'm not sure whether NPCs are like blocks in this regard.Rednaxela wrote:I'm rather certain that 5000 for NPCs that it reports is correct, at least for runtime spawning. The others I don't know about.
