• Locked Locked
  • Replies 21 replies
  • Subscribers 136 subscribers
  • Views 20587 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Shader Development Studio Problem

Mykhailo Kromarenko
Note: This was originally posted on 12th May 2011 at http://forums.arm.com

Hello,
Recently I decided to try out Mali Developer Tools, which look very promising.

Unfortunately I have a problem with Shader Development Studio.
When trying to make SimpleTest Project (from the User Guide) while rendering the shader effect
the Shader Preview shows a triangle instead of a square shown in the Guide.
In general, it is not surprising, since the option VERTICES in Shader Attributes View has by default  three
vertices:
-1.0 -1.0,0.0,1.0,
1.0 -1.0,0.0,1.0,
1.0,1.0,0.0,1.0,

The problem however is that there is no possibility to add additional vertices
(when choosing the option USER_DEFINED). You can only change the three given.
Changing the geometry in Shader Control View do not bring any effect, always showing three vertices.
Even when using a Shader Examples from Mali GPU Shader Library shaders are applied to that triangle.
The shaders themselves are working (changing color, texturing, etc).

Plugin has been tested on the following configurations:
Eclipse 3.6.2
  • GeForce 9600M GT Windows 7 64bit
  • GeForce GTS 250 Windows 7 32bit

All necessary OpenGL extensions are present, Emulator and Offline Shader Compiler are installed and work.

[font=arial, sans-serif]Had someone the same problem and is there a solution?[/font]
[font=arial, sans-serif]Thanks.[/font]
Parents
  • Note: This was originally posted on 20th October 2011 at http://forums.arm.com

    Thanks, that's helpful!

    I don't feel that the two exceptions you mentioned are related to this problem; the first looks like an accidental call to set a previous renderer connection when none exists, and the second is someone trying to dispose an SWT widget that's already been disposed (both are bugs, and I've logged them in our bug tracker).

    My installation of Eclipse was also a fresh 3.7, running on Java 6. I haven't tried it on Java 7 yet. Maybe you're on to something there. I'll try to install Java 7 and try to reproduce it.

    In answer to your questions; I installed everything to the default locations and haven't made any changes to the PATH etc that weren't made by the installers themselves (i.e. adding the OpenGL ES 2.0 Emulator to the PATH).
Reply
  • Note: This was originally posted on 20th October 2011 at http://forums.arm.com

    Thanks, that's helpful!

    I don't feel that the two exceptions you mentioned are related to this problem; the first looks like an accidental call to set a previous renderer connection when none exists, and the second is someone trying to dispose an SWT widget that's already been disposed (both are bugs, and I've logged them in our bug tracker).

    My installation of Eclipse was also a fresh 3.7, running on Java 6. I haven't tried it on Java 7 yet. Maybe you're on to something there. I'll try to install Java 7 and try to reproduce it.

    In answer to your questions; I installed everything to the default locations and haven't made any changes to the PATH etc that weren't made by the installers themselves (i.e. adding the OpenGL ES 2.0 Emulator to the PATH).
Children
No data