Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Are you unchecking the checkbox to consume trains? If you do that, the portal will only produce instead of consume.They are only set to produce trains. I have tried the built-in portals, like Portal, and Portal Basic. I have also tried rules, such as Central Portal Control and Un-Portal 3 Extended, but they all seem to have the same limit of how many consists you can add. I am guessing that they all use the same portal script since they all get that error at the same point.
Sorry for explaining it poorly, but I meant setting up the portal with trains. I have a few very long consists that I want to configure the portal to emit, however, after a certain amount of consists are added, the portal throws up the "property browser refresh not handled" error, rendering it unusableAre you unchecking the checkbox to consume trains? If you do that, the portal will only produce instead of consume.
Is this just per one single portal or is it all portals combined ?It seems that all portals that I use have the same limit of "things" I can put in it. If I add too many items into the portal, I get the "Property Browser Refresh not handled" error. Whether it's Central Portal Control, Un-Portal, Portal Basic, etc... Does anybody know of a portal or rule that doesn't suffer this problem?
That's a script error caused by an update. Try using these. I know they work and have been updated a few versions ago and these are built-in.Sorry for explaining it poorly, but I meant setting up the portal with trains. I have a few very long consists that I want to configure the portal to emit, however, after a certain amount of consists are added, the portal throws up the "property browser refresh not handled" error, rendering it unusable
It only affects the portal I was currently working on.Is this just per one single portal or is it all portals combined
I have also tried the Built-in portals, and they have the same "property browser refresh not handled" problem. The only solution that I have found is to either shorten the length of the consists or have fewer of them.That's a script error caused by an update. Try using these. I know they work and have been updated a few versions ago and these are built-in.
<kuid2:30501:22006:5> Portal Basic
<kuid:-25:1264> Portal
Other portals have issues with them due to the script not being updated or due to them having other features that now make them incompatible. Not being built-in means, they need to be updated by their respective authors unless they are on the repair list, most likely this is the case, for the Content Repair Group to work on.
This isn't right. There appears to be something else going on. I recommend running a database repair. That may fix this issue for you.It only affects the portal I was currently working on.
I have also tried the Built-in portals, and they have the same "property browser refresh not handled" problem. The only solution that I have found is to either shorten the length of the consists or have fewer of them.
Maybe as an alternative, run another siding in next to your portal and put another one in to help make up the difference.I appreciate all of the assistance everyone has given, but I will stop pursuing this matter.
Yeah, that would work, then I could use Central Portal Control to configure both portals as one.Maybe as an alternative, run another siding in next to your portal and put another one in to help make up the difference.