gDEBugger new version is out. We would like your feedback

[Graphic Remedy]

Hi All

gDEBugger version 1.2 has been released. This new version adds an interactive texture viewer, an improved HTML log file and a lot of other changes.
Please download it from www.gremedy.com and give us your comment.

We are currently releasing a new version of gDEBugger every ~ 1.5 month. We have a lot of new features and enhancements in mind, but we would like to hear your inputs on:

a. Which features would like us to improve / change?
b. Which features should be added?
c. What are the annoying things?
d. Are there bugs / usability problems that disable you from using gDEBugger?
e. Any good words :-)

I encourage you to use this page and give us your feedback.

We will do our best to make gDEBugger as useful and productive as we can.

The gDEBugger team
www.gremedy.com

[Gorg]

It is not working very much for me right now.

The gui shows nothing but logging to file works though.

There seems to be a small problem with the images link though. Looks like mozilla does not like the .\.
file:///C:/Documents%20and%20Settings/Eric/Local%20Settings/Temp/Engine-Thursday_27_January_2005-20_21_55/.\CContext2-Texture2-LOD0-2D.tif

By the way, the image beside the texture call is an awesome feature. I have been sloppy and so I can see my random binding pattern !

I would like to be able to pick a directory for the logs. I don't like to dig very deep in my directory structure.

Little less important, but I think grayscale textures should stay grayscale instead of putting the color in the red channel. Simply put the color value in all color channel would do the trick.

[sqrt[-1]]

To :Gorg
I assume you have tried http://glintercept.nutty.org ?

I also could not get the image view to display any images.

It would probably be a good idea to allow people to save the log in text as well as html as it makes it easier when running diff programs on different runs.

Perhaps making the deirectory where the logs are save to a bit more obvious (perhaps as part of the wizard?)

I might sugges the default image save format be other than .tif, as the browsers I tried did not seem to like it much. (broken image)

[Graphic Remedy]

Hi Gorg,

Originally posted by Gorg:
It is not working very much for me right now.

The gui shows nothing but logging to file works though.

The views display the information only when the process is suspended (F6).

If the process is suspended and you still face the same problem, please let us know the following:
1. Does it happen with all views or just with some of them?
2. Do you have the same problem with the "Graphic Remedy's teapot example"?
3. Do you have a sample program reproducing the problem, which you can send us for debugging?

There seems to be a small problem with the images link though. Looks like mozilla does not like the .\.
file:///C:/Documents%20and%20Settings/Eric/Local%20Settings/Temp/Engine-Thursday_27_January_2005-20_21_55/.\CContext2-Texture2-LOD0-2D.tif

It is not a mozilla '.\' specific problem. There is a problem to display Tiff files inside the browser. The default file format was defined as tiff (I changed the default when testing the application and forgot to change it back). You can change the file format in the options dialog. The version that is currently on the web server is fixed.

By the way, the image beside the texture call is an awesome feature. I have been sloppy and so I can see my random binding pattern !

I would like to be able to pick a directory for the logs. I don't like to dig very deep in my directory structure.

You can set the directory for the logs in the Debug Settings Dialog (CTRL-D). We will add it into the wizard in the next version.

Little less important, but I think grayscale textures should stay grayscale instead of putting the color in the red channel. Simply put the color value in all color channel would do the trick.

We will check this out.

The gDEBugger Team

[Graphic Remedy]

Originally posted by sqrt[-1]:


I also could not get the image view to display any images.

It would probably be a good idea to allow people to save the log in text as well as html as it makes it easier when running diff programs on different runs.

Perhaps making the directory where the logs are save to a bit more obvious (perhaps as part of the wizard?)

I might suggest the default image save format be other than .tif, as the browsers I tried did not seem to like it much. (broken image)

1. What have you got in the Texture Viewer when the textures could not be displayed?
2. Our html logging is very light html. It is basically text file with
instead of /n and link to the images where needed.
3. The default logs directory is the TEMP directory of the computer. As mentioned, we will add it into the wizard.
4. Fixed. The tif format was intended for 3D textures, GPGPU and cross platform use.

Regards,
The gDEBugger team

[supagu]

- i get a crash trying to look at my system specs
- also crash when changing to "front interactive"
(and it says i could view whats being rendered step by step, dont know where this is suppost to show up?)

im wondering if you could make a special programmers library so programmers can put in say some code:

gdebugComment("some random comment");

and you can break at these points also, this would allow users to set set points so they when a new frame is occuring, or if they want to analyse functions more indepth.

some profiling settings would be nifty 2. ie. how long a gl call takes.

[jide]

Windows 2000, Xp ???

What about other OSes ? Are there even plan to be supported ?

Here were my feedbacks.

[Graphic Remedy]

Hi supagu

- I get a crash trying to look at my system specs
- Also crash when changing to "front interactive"
(and it says i could view whats being rendered step by step, dont know where this is suppost to show up?)

These problems are new to us. Can we get a demo of your application for testing?
If this is not possible, can we send you a test version of gDEBugger?

im wondering if you could make a special programmers library so programmers can put in say some code:
gdebugComment("some random comment");

This mechanism was proposed to us by few users. We think its a good mechanism. We will implement it in one of our coming versions.

Some profiling settings would be nifty 2. ie. how long a gl call takes.

A lot of profiling abilities will get into the next gDEBugger version. All you have to do is wait for ~1 month

The gDEBugger team
www.gremedy.com

[Graphic Remedy]

Hi jide

Windows 2000, Xp ???
What about other OSes ? Are there even plan to be supported ?

gDEBugger infrastructure and GUI were written in a cross platform approach and are using cross platform components.
Since gDEBugger is a new product, we would first like to make it more robust and mature on Windows and then start porting it to other platforms.
The next platform will probably be Linux.

The gDEBugger team
http://www.gremedy.com

[sqrt[-1]]

I did not realise that you had to pause the app to get textures to display. Once I did this, they all showed up. (you may mention this in the docs, but perhaps having a "waiting for app to pause" or something in the texture dialog if it is brought up while the app is running?)