#Need Help with Game Circuits Hands-On
20 messages · Page 1 of 1 (latest)
( My username is @cursive token, message me beforehand so I know who to look for )
I feel bad for having to say this but I think the contest build phase ended a few days ago
Hopefully not, but it said on the contest page that " you must publish within 72 hours of the Play phase starting November~~ 11th~~ 18th, 12:00 am PDT. If you publish your room after 72 hours into the Play phase, your room will not be entered into the contest."
im trying to push it as far as i can, meaning for my time (CST), i have to publish by November 21st, 2:00am.
Honestly it's pretty stupid of me for even pushing it this far but i guess its too late to change that
No don’t worry we did the same thing
What type of issues are you having?
Ah, unfortunately I may not be much help there
I would say try to stop systems running simultaneously if you can but thats all I can say
this error appears constantly despite the entire map not including anything to do with object event receivers
I tried making the game very linear in terms of circuits, but it still does stuff like that and it's becoming depressing
headsup:
Its not the event receiver alone causing CPU overheat errors
Other chips are rasing the CPU ALOT, to the point that, when that event receiver fires, it fineally reaches 100% and errors
I know this, but the thing that confuses me is the fact that the event receiver doesn't even exist. No where in the map or my circuits are "object entered" chips being used or fired. I'm confused on why it does this when it isn't apart of my circuits. I wish it told me the real stopping point where it overheats instead of a weird object receiver
Event Receiver (Object Entered) is an event inside trigger volumes