HLS - Preview Graph...
 
Notifications
Clear all

HLS - Preview Graphics Card Debugging

5 Posts
4 Users
0 Reactions
1,725 Views
Posts: 3650
Topic starter
(@jhinkle)
Famed Member
Joined: 15 years ago
[#24505]

A user was not able to display the Pixels in the Preview Editor.

This has to do with the capabilities of the Graphics Card.

I have not yet found a solution to his issue but have generated a DebugGraphicsAdapter.txt file that is created any time you go into Preview or the Preview Editor.

If you are having a Preview Display issue --- get me that debug file.

The file will help identify what your issue is and if I can resolve it.

The file is located in the Library Folder under your HLS folder.

Thanks.

Joe


4 Replies
Posts: 629
(@dkulp)
Honorable Member
Joined: 14 years ago

I've attached the debug file created when I enter the preview from within Parallels on the Mac with full DirectX acceleration turned on. Again, the background bitmap shows and triangles show, but none of the pixels show.

(edit: added debug file with acceleration turned off which DOES allow the pixels to display, but pegs a CPU core)


Reply
jlowe
Posts: 952
(@jlowe)
Noble Member
Joined: 16 years ago

Very cool. HLS crashed on me the other day and I loved that it has a built in reporting system.


Reply
Posts: 3650
Topic starter
(@jhinkle)
Famed Member
Joined: 15 years ago
jlowe wrote:Very cool. HLS crashed on me the other day and I loved that it has a built in reporting system.

Programs crash for several reasons ...

#1. The user does something I NEVER thought they would ever do ... If what they did is BAD --- I can attempt to detect it and not let it happen.

This type is on-going as every one thinks differently.

#2. I make a mistake in the program. If I can identify it --- I can immediately fix it.

Very often the Debug data is not enough to tell me what someone did (Think #1 above). That is why I ask for you to put in information as to what you are doing etc.

Many time the debug data does not help but the text information allows me to pin-point the issue.

Joe


Reply
kingofkya
Posts: 2165
(@kingofkya)
Noble Member
Joined: 15 years ago
JHinkle wrote:Programs crash for several reasons ...

#1. The user does something I NEVER thought they would ever do ... If what they did is BAD --- I can attempt to detect it and not let it happen.

This type is on-going as every one thinks differently.

#2. I make a mistake in the program. If I can identify it --- I can immediately fix it.

Very often the Debug data is not enough to tell me what someone did (Think #1 above). That is why I ask for you to put in information as to what you are doing etc.

Many time the debug data does not help but the text information allows me to pin-point the issue.

Joe

I can help with number 1 🙂 I am sure I am not the only one


Reply
Share: