Archive: 6 posts

---

I have alot of wires in my sackbot for my upcoming level. Is there anyway to reduce the severe pauses that occur? It really is quite annoying to wait 30 seconds before I can hook up an AND gate to an input.

2013-11-19 05:47:00 Author: Felyne Posts: 25

---

Hi Felyne, Its happened to me too on occasion... even to the point of crashing my ps3. Here's a few ideas which may help. If you have A lot of wires runnig from 1 chip to another, reduce them by using tags/ tag sensors instead (eg, if you say, have L1 on transmitting control seat wired int L1 on the recieving sackbot control seat, remove the wire and have L1 going into a tag labelled L1. Then on the sackbot have a tag sensor detect R1 tag and have that wire into the L1 button input). CLOSE MICROCHIPS:- If your sackbot has a lot of chips connected by loads of wires, its gonnta be a week before you can open up a chip your working on... So... Label each chip and build the logic on it away from the sackbot. In other words, say for example your doing health, make all your health logic on that chip but just wire the health seatups output to the edge of the chip. then close the chip. You should notice that the connection that the output that is going to the edge of the chip should show up as a highlighted output tab even though the chip is closed. you can then copy and move the chip into place on the sackbot and then bring a wire from that health chips tab to where its to be connected. This means the chip wont be open and slowint things down. ZOOM IN:- If you zoom your camera right in as far as you can, it will speed things up a little as the screen isnt processing as much graphic information. SPACING:- When working on a few chips on a sackbot, open each chipboard and move them far away from each other, so theres less on screen at once. THe whole problem is the more you have displayed on a screen at once the more slow down there will be. so the less showing graphically, the better it will run. I hope this is of use . invite me if you need help my friend sean88

2013-11-19 15:28:00 Author: Sean88 Posts: 662

---

Use more microchips and try to space out your logic more. You can also remove the wire visibility and see if that helps.

2013-11-21 22:33:00 Author: Rpg Maker Posts: 877

---

Usually it's because your logic becomes overcomplex (this has happened to me several times) so the best thing to do is to organize your logic, and try and take out as much as you can without reducing the actual purpose of the logic, and if you cant, then I would try a new system of logic (I once had a weapon for a level that took up 3 1/2 thermo notches, until I swutch to a percent system, then after it barely took up 1/10 of a notch) If you cant think of any new systems I can try to help with what I can (I hope my advice helped you)

2013-11-27 16:11:00 Author: amiel445566 Posts: 664

---

Separate your logic. I used to have this problem with selectors, but if you put the selector in a microchip and the thing you're connecting it to in another microchip, there won't be any lag at all.

2013-12-01 16:58:00 Author: AmazingKittyCat Posts: 204

---

The pathfinding for wires in microchips causes the stutter. The solution is to simply build your circuits outside of microchips where no wire pathfinding is performed. I like the blackboard material best for building large circuits on.

2013-12-02 09:14:00 Author: Ayneh Posts: 2454

Posts: 1077139    Threads: 69970    Members: 9661    Archive-Date: 2019-01-19

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.