• Locked Locked
  • Replies 21 replies
  • Subscribers 137 subscribers
  • Views 21580 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 May 2011 at http://forums.arm.com

    Yes, in general the version of windows should not play a special role here, but I was able to try the plugin
    on the third computer with windows 7 already (albeit with similar characteristics that were given above)
    on a clean eclipse installation. The problem is the same.

    About adding additional vertices, I just wanted to add a fourth vertex to the three present, in order to
    turn it into a square, but in principle, several different meshes should be sufficient for shader testing.
    Speaking about the three vertices, I proceed from the fact that VERTICES variable represent 3 homogeneous vertices
    (one in each row). Since I am not sure, here is a picture
     
    In error log I found two errors related to the plugin:

    The first one happened rarely apparently at the opening of a (closed) project:

    Message: Unhandled event loop exception

    Stack Trace:
    java.lang.NullPointerException
    at com.arm.mali.shaderdebugger.preview.PreviewModel.redrawPreviewImage(PreviewModel.java:542)
    at com.arm.mali.shaderdebugger.preview.PreviewModel$1.run(PreviewModel.java:596)
    at org.eclipse.swt.widgets.Display.runTimer(Display.java:4167)
    at org.eclipse.swt.widgets.Display.messageProc(Display.java:3256)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2459)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

    [size="2"]As well as a "Widget is disposed", when closing eclipse with an opened shader studio project.

    When I try to change geometry simply nothing happens, there are no logged errors in this case.[/size]
Reply
  • Note: This was originally posted on 20th May 2011 at http://forums.arm.com

    Yes, in general the version of windows should not play a special role here, but I was able to try the plugin
    on the third computer with windows 7 already (albeit with similar characteristics that were given above)
    on a clean eclipse installation. The problem is the same.

    About adding additional vertices, I just wanted to add a fourth vertex to the three present, in order to
    turn it into a square, but in principle, several different meshes should be sufficient for shader testing.
    Speaking about the three vertices, I proceed from the fact that VERTICES variable represent 3 homogeneous vertices
    (one in each row). Since I am not sure, here is a picture
     
    In error log I found two errors related to the plugin:

    The first one happened rarely apparently at the opening of a (closed) project:

    Message: Unhandled event loop exception

    Stack Trace:
    java.lang.NullPointerException
    at com.arm.mali.shaderdebugger.preview.PreviewModel.redrawPreviewImage(PreviewModel.java:542)
    at com.arm.mali.shaderdebugger.preview.PreviewModel$1.run(PreviewModel.java:596)
    at org.eclipse.swt.widgets.Display.runTimer(Display.java:4167)
    at org.eclipse.swt.widgets.Display.messageProc(Display.java:3256)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2459)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

    [size="2"]As well as a "Widget is disposed", when closing eclipse with an opened shader studio project.

    When I try to change geometry simply nothing happens, there are no logged errors in this case.[/size]
Children
No data