Author Topic: Freeze on loading Hyldaa Plaza  (Read 1138 times)

Cha0s

  • Veteran
  • *
  • Posts: 1860
    • View Profile
Freeze on loading Hyldaa Plaza
« on: December 09, 2004, 03:04:10 am »
Since I couldn\'t get character creation to work, I decided to give it a whirl with my PC-created character. I selected him, clicked \"Join,\" got the loading window, had the MOTD load, then... nothing. The loading bar didn\'t move. Even after 5 straight minutes of waiting. Here\'s the dump:

ProcessLighting:
  Sector \'laanx_dungeon\' for ambient light was not found in lighting setup 11.

  Sector \'jayose_inside\' for ambient light was not found in lighting setup 11.

  Sector \'laanx_entrance\' for ambient light was not found in lighting setup
  11.


ProcessLighting:
  Light \'crystallaanx_entrance\' was not found in lighting setup 11.

ProcessLighting:
  Sector \'laanx_main\' for ambient light was not found in lighting setup 11.

  Sector \'laanx_well\' for ambient light was not found in lighting setup 11.


ProcessLighting:
  Light \'Omni35hydlaa_plaza\' was not found in lighting setup 11.
  Light \'Omni36hydlaa_plaza\' was not found in lighting setup 11.
  Light \'Omni37hydlaa_plaza\' was not found in lighting setup 11.
  Light \'Omni38hydlaa_plaza\' was not found in lighting setup 11.
  Light \'Omni39hydlaa_plaza\' was not found in lighting setup 11.
  Light \'Omni40hydlaa_plaza\' was not found in lighting setup 11.
  Light \'Omni41hydlaa_plaza\' was not found in lighting setup 11.
  Light \'Omni42hydlaa_plaza\' was not found in lighting setup 11.
  Light \'crystalhydlaa_plaza\' was not found in lighting setup 11.

ProcessLighting:
  Sector \'hydlaa_plaza\' for ambient light was not found in lighting setup 11.

  Sector \'tavern_de_kadel\' for ambient light was not found in lighting setup
  11.

  Sector \'windowless_tower\' for ambient light was not found in lighting setup
  11.

  Sector \'windowless_tower_dungeon\' for ambient light was not found in
  lighting setup 11.

  Sector \'windowless_tower_exit\' for ambient light was not found in lighting
  setup 11.


ProcessLighting:
  Light \'L060_74_164_177_500windowless_tower_top\' was not found in lighting
  setup 11.
  Light \'sun_02windowless_tower_top\' was not found in lighting setup 11.

ProcessLighting:
  Sector \'windowless_tower_top\' for ambient light was not found in lighting
  setup 11.


ProcessLighting:
  Light \'crystalwindowless_tower_top\' was not found in lighting setup 11.

planeshift.application.client:
  PSLoader: step 2: success

ParseFile:
  Could not find file: /planeshift/world/podium/sound.xml

planeshift.application.client:
  PSLoader: step 3: success
Cha0s
Mac OS X Forum Moderator
In-Game Roleplay Forum Moderator
Please search and skim existing threads before posting!

Mosfet

  • Traveller
  • *
  • Posts: 43
    • View Profile
(No subject)
« Reply #1 on: December 11, 2004, 05:33:35 pm »
After running the Updater, I now get this too.

Vaiyul

  • Traveller
  • *
  • Posts: 15
    • View Profile
(No subject)
« Reply #2 on: December 11, 2004, 07:26:26 pm »
I have the same problem with the updated version, so I renamed the folder and reinstalled the original MacOSX version of the game.....I get the same problem after character selection screen, the usual load screen and the game is stuck with the \"requesting world\" dialog. So I dumped the /sw folder created by Fink, and reinstalled everything from scratch: Fink 0.7.1, through Finkcommander I installed the missing libvorbis0-shlibs file, ran the psclient.app and end up having the same problem freeze on \"requesting world\".

could it be a server compatibility problem, like incompatible client (before or after update) with the current server requests..... just guessing here.
Planeshift version: PlaneShift_CBV0.3.005_macosx
OS: 10.3.8
Computer: 800Mhz iMac 17\"Flat Pannel
Ram : 512 Mo
Video Card: NVidia GForce4 MX, 32MoVRAM

Client setup: 1440x900 FullScreen


dfryer

  • Veteran
  • *
  • Posts: 1070
    • View Profile
(No subject)
« Reply #3 on: December 12, 2004, 05:55:09 am »
The old version failing to work is probably indicitave that there\'s some server change that is triggering this, but we\'re not smart enough to detect it automatically.
Quidquid latine dictum sit, altum sonatur.