Plugin :Shockwave 8 This bug appeared when bug bug 56297 was fixed. Steps : 1 Go to the shockwave page and load Tank Wars game from Arcade Action inside Games 2 Select "Low bandwidth" and let the game load 3 Click on Start Game 4 Observe that keyboard does not work and you cannot play the game 5 Also, in step2 , if I select "High banwidth" , my machine freezes while the game is loading.

mac only, nominating for beta1.

cc: Saari

how can I test this with Shockwave blocking us?

Chris, 1. Hand-edit Netscape 6\defaults\pref\all-ns.js, add this line, and save; this causes N6 to report itself as Nav4.75. Then you can visit shockwave.com pref("general.useragent.override","Mozilla/4.75 [en] (Win95; U)");

You may also need to complete Shockwave registration by visiting any Shockwave content with 4.x first. However, Chris won't the patch in bug 65687 fix this?

With or without the patch applied, I can't seem to get Tankwars working at all on the Mac. I either crash with an access fault exception inside their plugin or their plugin reports a "Director Player Error, Property not found, #type" and quits. I need Macromedia's help to idetify why their plugin crashes or reports these errors.

This seems to be related to the bigger issue of the keyboard not working on the Mac for Flash or Shockwave. Asking Peter Grandmaison to provide more info if possible.

Meredith, I just checked in code that allows key events to go to flash and shockwave plugins on Mac, so that isn't the only issue.

So, the code you have added solves the keyboard interaction issue on the Mac for both Flash and Shockwave, excluding the Tank Wars movie? I would seuggest contacting Peter Grandmaison, grandma@macromedia.com, to discuss this further.

TankWars is still crashing for me on loading. Stack trace isn't very helpful. Peter, could you point me in the right direction as to why this is crashing on Mac in Shockwave? Thanks.

Changing summary from: keyboard does not work on Tank Wars Game on shockwave.com page as keyboard events are now being sent to plugins on the Mac, but we crash on the last "loading" phase of Tank Wars.

I am able to load Tank Wars if I use SW 8.5, and if I use SW 8.0 with a large partition. Maybe you should try both of these things. (note I filed 68756 as keyboard input in shockwave is broken, so you cannot play the game, but you can click around to see it is working).

I'm marking this bug INVALID because the solution to the crash is to either to upgrade to SW8.5 or increase the memory allocated to Mozilla. The plugin is simply running out of memory. Angela/Eric: The MacDev list has been lobbying to increase the default memory allocated for Netscape on the Mac. This is another good reason to do that.

Reopening.

Reassigning to angelabu and moving to installer component. We need to increase the default memory allocted to Netscape on Mac.

I think the Shockwave installler when made "Netscape 6/Mozilla" aware will do this as it does in 4.x.

Marek wanted this one -- reassigning to Marek. -- AKR

assigning to sdagley

Set minimum to 26MB, preferred to 32MB

after discussion with sfraser, minimum 20, preferred 28

who do we cc: in the docs group so this makes it into the release notes?

sr=sfraser on the project change for this.

Rel Notes-->Adding rudman to the cc: list. .Angela...

Changes from comment of 2001-04-16 12:59 checked in. Do I mark this as fixed or wait for the doc folks to pick up on the relnote tag?

Adding Jatin for release note heads up. Mark as fixed; we'll open a relnote tracking bug and appropriate text can be put there (we'll catch this because of the keyword, but the tracking bug contains the actual text in the relnotes---sdagley, no action required on your part other than closing the bug).

thanks Steve, marking fixed now

verified that the minimum and preferred mem sizes are 20 and 28 mb respectively in build 0423 trunk on mac. Pls note: even after using the 8.5 installer on mac, I was prompted with a message saying 'the installer will increase the memory of the application....'

I'll get in touch w./ elleN at Macromedia and ask her about the Mac installer. Peter Grandmaison, now that we've raised memory size, do you still need to increase memory of the application?

Note that the 28MB preferred setting was chosen to allow us to load a typical page w/o having to allocate memory out of temp mem. If some plugin needs more memory in the app heap (usually they shouldn't if they're using our memory allocators) they'll need to have their installer increase our memory partition but we're not going to make the default any bigger.