This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
Gunner76th's profile picture

[1.7.10][SMP] Client crashes when rendering computer after using Enhanced Portal

Started by Gunner76th, 23 October 2014 - 06:50 PM
Gunner76th #1
Posted 23 October 2014 - 08:50 PM
Version:

ComputerCraft 1.6.4pr6

Description: When using an Enhanced portal to return to my base (which is chunk loaded via a Railcraft Admin Anchor) my client crashes back to the launcher with the following crash report due to rendering: http://pastebin.com/4hhT8RZP

Expected result:

I walk through my portal to return to my base, and my client not crash.

Reproduction Steps:

I have 2 advanced computers, 3 wired modems, 3 sets of 2x3 advanced monitors. 1 advanced computer is running a Big Reactor control program, the second computer is running a Big Reactor monitoring and display program (gathers vitals on the reactor, and outputs it to the 2x3 monitors. Have entire setup chunk loaded by way of a Railcraft Admin anchor. Have an Enhanced Portals 3 portal in the same chunk loaded area as the computer setup, positioned in such a way in that, when you spawn, you are facing the computer setup.

Screenshot:

This is the view the player sees upon being spawned at my base when using an Enhanced Portals 3 portal.

https://dl.dropboxusercontent.com/u/251115511/Photos/2014-10-23_15.48.00.png


This bug report has been cross posted to the Enhanced Portals 3 github bug reporting system. https://github.com/SkyNetAB/enhanced-portals/issues/161
Bomb Bloke #2
Posted 23 October 2014 - 10:52 PM
I suggest updating to ComputerCraft 1.65, then review this report if you continue to have problems.
Cranium #3
Posted 23 October 2014 - 11:04 PM
Indeed, much of the crashes were fixed upon release, so you definitely want to update.
Gunner76th #4
Posted 23 October 2014 - 11:33 PM
Just updated server and client to 1.6.5, and re-attempted the same event, and as before client crashed. http://pastebin.com/SfyeA4da

Strange thing is, this is only happening if I use the portal from an Overworld location back to my base. If I use my enhanced portal I have in the Nether to return, my client does not crash.
Bomb Bloke #5
Posted 24 October 2014 - 07:05 AM
What if you nip into creative move, and use the tp command to teleport yourself around? Can that still trigger crashes?
Gunner76th #6
Posted 27 October 2014 - 09:41 AM
I just tested using a TP command from the location of the overworld that my portal leads to, back to my base (portal was offline, and not used. I used tp as requested.) and the client still crashed. http://pastebin.com/U3izcYpX I had also removed the item in the previous crash report at the cords listed, but as you can see, a different location triggered the crash this time. I would appear that for some reason, it is crashing the clients when it goes to render the monitor. I have a couple more tests I plan to run dealing with TP and LOS. I will update on my findings.
Bomb Bloke #7
Posted 27 October 2014 - 11:05 AM
It'd be worthwhile running those tests without the Enhanced Portal mod installed at all.
Gunner76th #8
Posted 27 October 2014 - 04:17 PM
I can try that, however seeing as the crash happened when the portal was offline, while using a vanilla server command, I can not see how Enhanced Portals is a cause to the crash at this point. I will also be testing this in SSP mode as well, to see if this only occurs when running on a server, or if it occurs all the time.
Gunner76th #9
Posted 27 October 2014 - 07:40 PM
So I have completed the LOS test, and can confirm that the crash does not happen if the player does not have Line Of Sight to anything computer craft. I was able to test this as I have 2 rooms on the same level about 10 blocks away, and when TPing into that room, I do not crash. This was with Enhanced Portals mod still on the server. However, when I TP'd to the room containing the computer setup, my client crashed same as before. This is definitely an issue with the peripherals being rendered when the player "spawns" (either through TP or other means) within LOS of the peripherals, causing a rendering crash.