Web Start and Java2D performance properties

Newbie & Debugging Questions
#1

Has anybody else noticed that Web Start ignores the Java2D performance properties (like ‘ddscale’, ‘transaccel’ and ‘ddforcevram’) in an application the first time it is run after a download/update?

I noticed this when the logging messages were missing from web start console when I run my app for the first time. Subsequent runs produce some of those messages (but it’s missing/ignoring the messages for ‘ddscale’ and ‘ddforcevram’).

I’d appreciate a solution/workaround if somebody has one. Thanks.

EDIT:
Forgot to mention that I was using web start ver 1.4.2_04 and JRE 1.4.2_04 on a Windows Platform.

#2

it seems that when webstart launches the program, java2D is already inited and subsequent property changes are not taken in account. Got that problem very recently with java2D’opengl flag and nothing worked. :’(

#3

[quote]it seems that when webstart launches the program, java2D is already inited and subsequent property changes are not taken in account. Got that problem very recently with java2D’opengl flag and nothing worked. :’(
[/quote]
Aha. So you notice the same thing as well.

But it does work for subsequent runs, correct?

#4

not that i found, no.

#5

You probably are but just to check, you were running JRE 1.5 right?

Anyway, if you want to test: www.benyeoh.com/bentris2.jnlp

1st time it launches and you’ll get unaccelerated FPS.

Subsequent runs and you’ll get accelerated FPS.

#6

Yes, i’m using 1.5.

there was an error, can’t locate http://www.benyeoh.com/bgimages.jar which is weird because that Jar exists… 1.5 jaws bug?

#7

[quote]Yes, i’m using 1.5.

there was an error, can’t locate http://www.benyeoh.com/bgimages.jar which is weird because that Jar exists… 1.5 jaws bug?
[/quote]
Looks like it. I’m using 1.4.2 and I run it off web start just fine.

Does web start still allow you to continue after the error?