I'm now sure that the Multistage behavior causes the crash because the SmartSeek before it doesn't work.
I'm also almost sure I know the fix.
In the Python File, line 55-56, the Behaviors are attributed with:
- Code: Select all
sTubeMulti = ptAttribBehavior(43, 's tube entry multi', netForce=0)
nTubeMulti = ptAttribBehavior(44, 'n tube entry multi', netForce=0)
In every other Python file I looked in, they use netForce=1, or uses the default value, which is 1.
So, maybe you should try with:
- Code: Select all
sTubeMulti = ptAttribBehavior(43, 's tube entry multi', netForce=1)
nTubeMulti = ptAttribBehavior(44, 'n tube entry multi', netForce=1)
AND at line ~910:
- Code: Select all
if (id == nTubeEntry.id):
trigger = PtFindAvatar(events)
print 'entered team 1 tube, run behavior'
ageSDL.setIndex('nWallPlayer', 0, PtGetClientIDFromAvatarKey(trigger.getKey()))
trigger.avatar.runBehaviorSetNotify(nTubeMulti.value, self.key, 1) ##changed
if (id == sTubeEntry.id):
trigger = PtFindAvatar(events)
print 'entered team 2 tube, run behavior'
ageSDL.setIndex('sWallPlayer', 0, PtGetClientIDFromAvatarKey(trigger.getKey()))
trigger.avatar.runBehaviorSetNotify(sTubeMulti.value, self.key, 1) ##changed
(here I changed the 0 at the end to a 1, that's again the netForce flag)
diafero wrote:Okay, this seems to basically work offline, after I figured out how to use that weird console
That's why they added journals in the observation rooms, and added new textures to the panel in MOULa. It's far from being intuitive.
diafero wrote:The only other issues I experienced so far are related to the control panel: As soon as I click some area that is not clickable (for example, one of the black squares between the lines you can put the blockers on), the avatar leaves the chair. That's quite annoying as I keep accidentally hitting those...
That's a problem with the SittingModifier. That's its default behavior.
diafero wrote:Besides, (some of) the buttons on the panel can even be operated when I am not sitting on the chair... is that meant to happen? IMHO the other Uru panels do not allow that, you have to click them (or the chair in front of them) to be able to operate them.
Yes, the region is too big.
If you want, I can fix these. I could use another Multistage Behavior for the chairs, controlled by Python to exit only when you press the right/down/left key. That would be again more lines in the Python file, but it can be done. For the buttons, I can change the region in which you must be to activate them (there is another one for the big button which is a lot smaller)... or edit the region.
For now I think it doesn't really matter.