on. I can think of server side apps that could use a
fast
graphics pipeline to ship chunks of graphical
information
to a client using a high speed network. You have the
big
iron running the graphics and the client displaying
the
computed image. Things like molecular physics; GIS
If you're talking about a full immersive virtual reality environment,
then yes maybe VR isn't a consideration for Java2d. But for some limited
uses similar to Quicktime VR it is definitely applicable. I believe Ken
has an applet on the web that does exactly that in java.
As far as server-side
processing in software could benefit from porting
their operations to
the GPU -- regardless of whether those pixels are
going straight to the
display or coming back out of VRAM to be written to a
file.
Yes I know gpgpu and yes I've already on such a project, I also have some posts
in their
[EMAIL PROTECTED] wrote:
processing in software could benefit from porting
their operations to
the GPU -- regardless of whether those pixels are
going straight to the
display or coming back out of VRAM to be written to a
file.
Yes I know gpgpu and yes I've already on such a project, I also
[quote]
Is fundamentally wrong -- at least in my case.
[/quote]
I tend to hate such heuristic desicisions - I was hit by them in the oppsite
way:
I have a Core2Duo Laptop with 2GB Ram running Linux - so by default the
server-jvm is used for my desktop applications and even for Applets and small
[quote]
Then have higher level layers of graphic acceleration
for the more advanced video cards. Shading etc.
[/quote]
Well I think some kind of black-listing would probably the best thing -
black-list which driver/os/directx-versions are known to be broken and emit a small
warning on the
The funny thing is that Windows 2000 wasn't a server class OS
when I bought it. It was just the latest Windows. Somewhere
along the line it became a server OS. And I didn't know
I became an Administrator. I guess I didn't get the memo.
And the reason I don't upgrade to XP or (yuk) Vista is
Ken,
Please read the subject line.
Windows 2003 and 2008 are server OSes and are quite different
than windows 2000.
-phil.
Ken Warner wrote:
The funny thing is that Windows 2000 wasn't a server class OS
when I bought it. It was just the latest Windows. Somewhere
along the line it became a
I'm just going by what Dmitri told me...
Secondly, starting with b08 the pipeline will only be enabled
on client-class OS (WinXP and newer). Win2K* are classified as
a server-class OS flavor.
The reason for this policy is that typically on servers people
care more about stability than
One last thing then I'll say no more.
Seems to me that the way to include / exclude systems is
by the capabilities of the graphics card that Java is running
on. I can think of server side apps that could use a fast
graphics pipeline to ship chunks of graphical information
to a client using a
Hi James,
yes, the d3d pipeline is disabled on Windows 2003,
and starting with build 08 on any server-class OS
(for example Windows Server 2008).
The reason is that typically people don't care about
graphics performance on a server, and also drivers
tend to be old/buggy on servers
The assumption that,
...typically people don't care about
graphics performance on a server, and also drivers
tend to be old/buggy on servers as they are not
updated as often.
Is fundamentally wrong -- at least in my case.
I keep my machine as up to date
as possible. I installed the
Hello
I got [W] GetFlagValues: D3D is disabled on Win Server 2003 while set
J2D_TRACE_LEVEL=4
Is it the default behaviour or I can force to enable it in windows 2003?
thanks in advance!
James
[Message sent by forum member 'inchlin' (inchlin)]
13 matches
Mail list logo
