GearHeads Forum

Art

I've loaded V10B. Same results of the belt not showing. I'll continue to look at my system just to make sure that I hadn't turned off some setting. I never use my computer for interactive games so I'll start exploring if there are any gaming specific options on the computer.

Bill

TickerLog excerpt:
er\modeldatabase.cpp(119): Initializing belt data.
er\modeldatabase.cpp(227): Initializing belt motion contour.
ker\ticker\model.cpp(769): Mesh Create: belt
ker\ticker\model.cpp(792): Mesh Stage2: belt
ker\ticker\model.cpp(801): Mesh Stage 3: belt
ker\ticker\model.cpp(809): Mesh Stage4: belt
ker\ticker\model.cpp(769): Mesh Create: belt
ker\ticker\model.cpp(811): end Mesh Create: belt
er\modeldatabase.cpp(242): Initializing belt Shader. #1
er\modeldatabase.cpp(249): Initializing belt Shader. #2
er\ticker\drawable.h(85): Instanced Object init.
\tekniquemanager.cpp(161): Instanced Binding
\tekniquemanager.cpp(166): Instanced Binding complete
\tekniquemanager.cpp(210): Instance Shader Init
ker\vertexshader.cpp(25): Instanced Shader loading
ker\vertexshader.cpp(32): Instanced Shader blob size: 61260
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
ker\vertexshader.cpp(43): Instanced Shader blob failed: -2147024809
\tekniquemanager.cpp(212): Instance Shader complete
\tekniquemanager.cpp(216): Instance Shader 2 complete
\tekniquemanager.cpp(220): pvs complete
\tekniquemanager.cpp(224): tcb
\tekniquemanager.cpp(228): mats complete
er\modeldatabase.cpp(252): Initializing belt Shader. #3
er\modeldatabase.cpp(268): Initializing belt Shader.
er\modeldatabase.cpp(278): Initializing belt constraints.
er\modeldatabase.cpp(288): Initializing belt complete.
icker\tickerview.cpp(177): Remove Objects.
er\ticker\ticker.cpp(262): Exit App.
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))

Bill:

Version 1.10b is online and should show me exactly what the system error code is that is failing the shader. This should allow
me to get my teeth deeper into the culprit. We're very close I think, I kinda feel it will be something stupid on my part as a
missing support file or something. Ticker is video game tech really, its written in the same way as a video game but attached to
an application interface, so its a bit of a strange marriage as far as timing relationships in the code. As this is my first "Video game"
type of program of this size and nature, I expect I missed something somewhere as the belts are the only item that do as they do
in terms of communication between the graphics card and the program. Its the only time I've used the video card as a computation
unit and was interesting in terms of making it work. (Thats always a dangerous sign for systemic reliability across various hardware).

Hopefully this leads to a solution finally after all this testing. Thanks to you however, the error system is now much
more robust and corrective.

Art

Thanks Bill:

Thats plenty of power. The next version will record the actual error codes from the DX subsystem, so that may lead me
to a solution. Ill try to make it out by tomorrow.

Art

Art

My Computer has an Intel Core7 11th generation processor, 2.68GHz. The computer has 16Gbytes of memory and 32Gbytes of virtual memory.

The Video system is an Intel iRISx Max Graphics card. This evening I downloaded updated drivers for the card.

I re-ran Ticker with pulleys but the belt still did not display.

Bill

Bill:

It seems the error is coming from the DX11 subsystem in windows when I attempt to create the
instance shader on your machine. There was a guid error in instance shaders a while back. What version
of windows is this and what is your video card type? It will allow me to investigate why a system might reject a
call to this type of shader.
As we get more feedback I can determine if this is systemic, or some esoteric code call that only some
systems hate or like. I use a rdx2070S as my card and its rather powerful compared to may older cards,
so I'm hoping it isn't a card issue. It may be a driver issue if you haven't updated the video driver in
some time.

Thanks for the tests,

Art

Art

I've loaded v1.09B. The results are the same. I do have the file PBRVertexInstancedShader.cso on my system.

Bill

Tickerlog excerpt:

er\modeldatabase.cpp(119): Initializing belt data.
er\modeldatabase.cpp(227): Initializing belt motion contour.
ker\ticker\model.cpp(769): Mesh Create: belt
ker\ticker\model.cpp(792): Mesh Stage2: belt
ker\ticker\model.cpp(801): Mesh Stage 3: belt
ker\ticker\model.cpp(809): Mesh Stage4: belt
ker\ticker\model.cpp(769): Mesh Create: belt
ker\ticker\model.cpp(811): end Mesh Create: belt
er\modeldatabase.cpp(242): Initializing belt Shader. #1
er\modeldatabase.cpp(249): Initializing belt Shader. #2
er\ticker\drawable.h(85): Instanced Object init.
\tekniquemanager.cpp(161): Instanced Binding
\tekniquemanager.cpp(166): Instanced Binding complete
\tekniquemanager.cpp(210): Instance Shader Init
ker\vertexshader.cpp(22): Instanced Shader loading
ker\vertexshader.cpp(28): Instanced Shader blob size: 61260
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
\ticker\graphics.cpp(305):
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
\tekniquemanager.cpp(234): Shade Failed
er\modeldatabase.cpp(252): Initializing belt Shader. #3
er\modeldatabase.cpp(268): Initializing belt Shader.
er\modeldatabase.cpp(278): Initializing belt constraints.
er\modeldatabase.cpp(288): Initializing belt complete.
icker\tickerview.cpp(177): Remove Objects.
er\ticker\ticker.cpp(262): Exit App.
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))

Interesting log. Its pointing to your system refusing to maker the shader from its blob.
I ve added a few debugs so I can see where its failing. I can duplicate your error by deleting the
file PBRVertexInstancedShader.cso in the shaderbins folder. (That files does exist on your system right? )

V1.09b is online to test that theory.
In any event, this log will tell me the size of your shader blob and if its failing on its load or its creation.

Thanks
Art

Art:

I loaded v08B. The belts still do not display but are there if I turn on Wireframe during the simulation run.


Bill

Ticker log file excerpt:

er\modeldatabase.cpp(119): Initializing belt data.
er\modeldatabase.cpp(227): Initializing belt motion contour.
ker\ticker\model.cpp(769): Mesh Create: belt
ker\ticker\model.cpp(792): Mesh Stage2: belt
ker\ticker\model.cpp(801): Mesh Stage 3: belt
ker\ticker\model.cpp(809): Mesh Stage4: belt
ker\ticker\model.cpp(769): Mesh Create: belt
ker\ticker\model.cpp(811): end Mesh Create: belt
er\modeldatabase.cpp(242): Initializing belt Shader. #1
er\modeldatabase.cpp(249): Initializing belt Shader. #2
er\ticker\drawable.h(85): Instanced Object init.
\tekniquemanager.cpp(161): Instanced Binding
\tekniquemanager.cpp(166): Instanced Binding complete
\tekniquemanager.cpp(198): LUT complete
\tekniquemanager.cpp(200): Trilinear Sampler complete
\tekniquemanager.cpp(210): Instance Shader Init
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
\ticker\graphics.cpp(305):
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
\tekniquemanager.cpp(234): Shade Failed
er\modeldatabase.cpp(252): Initializing belt Shader. #3
er\modeldatabase.cpp(268): Initializing belt Shader.
er\modeldatabase.cpp(278): Initializing belt constraints.
er\modeldatabase.cpp(288): Initializing belt complete.
icker\tickerview.cpp(177): Remove Objects.
er\ticker\ticker.cpp(262): Exit App.
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))
er\ticker\ticker.cpp(71): Exception code: 0xe06d7363 ((null))

Bill:

Version 1.008B is online. Your log showed the belts were being initialized twice at creation, once as a default single entity , then properly
as an instanced entity which may be draw multiple times in the shader. Its very possible your system didn't like this, and mine was OK with it.
It also made the log read somewhat psychotically. This version proper only inits the belt once as an instanced object. The log reads more linearly now
so if this doesn't fix the trouble, I can at least see exactly where we're failing.

Thanks for that log, it led to seeing this fairly serious error on my part.

Art

Bill:

Thanks for the log, I will analyse it and create some fixes.

>> The ball launcher would only launch balls when Gravity was turned on. Is this normal?

Yes, I decided that without gravity launched articles would sit still, I forgot however that
it can launch things with a speed vector... so I will undo that and make them active even without gravity. Thanks for the comment.

Art