Subject:
|
Re: Mata-nui problems and some Mac stuff (was Re: Bionicle.com updated!)
|
Newsgroups:
|
lugnet.lego.direct
|
Date:
|
Thu, 10 May 2001 15:52:20 GMT
|
Viewed:
|
632 times
|
| |
|
|
<Long-no snips for flavor>
In lugnet.lego.direct, Tomas Clark writes:
> I don't believe it's a cookie problem as AFAIK the Mata Nui site doesn't >extremely slow while "saving the game," and some also seem to get >hung up on loading some of the game files. The new area of the island >*is* completely playable, and you *can* cure the sickness in Po-Koro -- I >just did it from home off my dialup connection. The problem that Ian >Constable mentions here >(http://news.lugnet.com/technic/bionicle/?n=437) is similar, a hang-up >caused by an incomplete load. It's more along the lines of a >communication problem between individual users' browsers and the >server. The system that autosaves your position on Mata Nui from a >Flash web page is very cool but not quite your run-of-the-mill website >technology.
If my log-in data is saved on a cookie, and that log-in data is what the
server references for the auto-save, then it seems to me that it IS a cookie
problem, ESPECIALLY when it is known to be true that problems are
non-existant when you play logged off. It seems that with certain
system/OS/browser combinations, the game hangs up while saving or loading
the next scene. The same kind of thing can be said for the S@H system not
recognizing the country already selected for shopping, or it's penchant for
ignoring the "Skip this screen" check box option.
All of this is fine, however. Don't get me wrong, I don't like it when it
happens, but it is simply impossible to make all things work for all users
on all systems-known fact. Sure, supposedly 'platform independent'
technology like Flash is supposed to cure these ills, but I'm too much of a
realist to believe that it's going to really work that way. The LEGO sites
work great, and play well. I just hate to loose the flow of the game when it
hangs up, you know?
> We're going to look into improving the speed, etc. but here's how you >can work around the problem in the meantime:
> 1. Play without saving your game, using the "PLAY NOW" option when you first enter the site. If you're already logged in you'll have to log out at
> https://club.lego.com/ -- this means you'll have to play from the >beginning, and won't be able to save your place, but if you just want to >play the Po-Koro quests, save the villagers in Ga-Koro quickly and >proceed. The game runs much faster without the save-game function, >as people have pointed out.
I've done this. BTW, I hate that I missed the fire adventure and can't ever
play it. I've never been there damnit, and they keep telling me I have. Even
starting from scratch this is already taken care of for me...
Unfortunately, the hang-up problem CAN occur in un-saved mode also, as
referenced by the fact that the game pulled it on me right at the end of the
adventure, and a reload brought me back...are you ready for this...the
stinkin' beach! Everything I had done gone with one click...oh well...
> 2. Use Internet Explorer on Windows. I know that's not very helpful, but
> that browser seems to have little or no problem gliding through the >game saves and so forth. I haven't tested extensively on Linux, but Macs >and Netscape both seem to be having some difficulty.
Umm...there's that LEGO 'Windows-centric" attitude surfacing again.
Seriously, better not to go there right now...
> 3. If you hit a snag, reload until it goes away. You *can* get it to go
> away, and you won't lose your position in the game -- that's stored >safely in our database under your username. If you talk to a Tohunga, >for instance, and get a blank dialogue box, just hit reload. If the same >thing happens again, empty your browser cache and reload. If it still >happens, try quitting and restarting the browser. In most cases what's >happened is that your browser hasn't fully loaded the dialogue file, so >you'll have to force it to fetch a new copy of that file from the server. In >some cases this may even happen if you don't have game-saving >turned on. You can also try using a different browser -- since your >save-game is stored on our servers, you can go to any computer, log in, >and resume where you left off.
Nope...in my experience, if you screw with the game until you force the game
to a black scene, you re-start at a black scene. The ONLY fix I have found
for this is to re-install Shockwave. It works EVERY time, and leads me to
believe that there is perhaps somethinng more to these problems than LEGO
and the users. Just a bug-in-the-ear to pass along to the development company.
> Hope that helps. Good luck vs. Nui-Jaga.
>
> Tomas Clark
> Producer, LEGO Direct
Tomas, notice that I'm not down on you, LEGO or the developers for this.
Please thank all involved for the work they have done that I am enjoying for
FREE (a little fact that seems to get WAY overlooked these days). I hope
some of this input might help. In fact, if anyone you have working on these
issues would like to contact me personally, I'd be more than happy to help
out. Just e-mail!
Matt
|
|
Message is in Reply To:
2 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
