Problem D3D9Surface.cpp - Line 1099 - CTD

Koloss

Weyland-Yutani Corp.
Donator
Joined
Apr 16, 2013
Messages
167
Reaction score
1
Points
16
Location
Krefeld
Guys,

a really, really, REALLY annoying bug just drives me crazy for a few days.

Problem is this:
I just established a geostationary orbit around earth. I would like to deploy the MTKS-SAT. So far so good.
I use the DGIV. I switch to the upper panel and empty the airlock. As soon as it reaches the 10% mark I get a CTD EVERY TIME.
The pop-up says something about the C++ runtime library and

Pop-up I'd like to punch in the face said:
Assertion Fail
D3D9surface.cpp
Line 1099

Expression: false

Any ideas?
I am using the D3D9 R15 client. Orbiter 2010, obviously...

Thanks for your help!
 
Last edited:

kuddel

Donator
Donator
Joined
Apr 1, 2008
Messages
2,064
Reaction score
507
Points
113
Hi Koloss,

from the info you gave I think it's a "Unable to perform blitting" issue.
The D3D9ClientLog[1] should also contain some lines like:
Code:
D3D9ClientSurface::CopyRect() Failed
Source Rect (%d,%d,%d,%d) (w=%u,h=%u) HANDLE=0x%X (%s)
Target Rect (%d,%d,%d,%d) (w=%u,h=%u) HANDLE=0x%X (%s)
...
with all the %s and %s giving a bit more of information.

Could you please post the parts of that log including the following several lines (that should give even more detailed information about the failed operation and operands)?

It's in an colorful HTML format, so the lines should be easy to find (first error line should be red)

And a scenario (the DGIV in GEO) to easily reproduce this would help a lot, too!

/Kuddel

[1] to be found at .\Modules\D3D9Client\D3D9ClientLog.html
 
Last edited:

Koloss

Weyland-Yutani Corp.
Donator
Joined
Apr 16, 2013
Messages
167
Reaction score
1
Points
16
Location
Krefeld
Hi Kuddel,

found it.
Here it is:

HTML:
(1099: 51.12s 258792662510us)(0x3378)[ERROR] UpdateSurface Blitting Failed 0x4DFCA50 (clbkCreateSurface) -> 0xD14B1F8 (clbkCreateSurface)
(1100: 51.12s 258792663558us)(0x3378)[ERROR] D3D9ClientSurface::CopyRect() Failed
(1101: 51.12s 258792664457us)(0x3378)Source Rect (0,0,-1,6) (w=1,h=6) HANDLE=0x4DFCA50 (clbkCreateSurface)
(1102: 51.12s 258792664474us)(0x3378)Target Rect (0,0,-1,6) (w=1,h=6) HANDLE=0xD14B1F8 (clbkCreateSurface)
(1103: 51.12s 258792664487us)(0x3378)Target name is clbkCreateSurface Handle=0xD14B1F8 (140,6)
(1104: 51.12s 258792664498us)(0x3378)Target Has a Surface Interface
(1105: 51.12s 258792664507us)(0x3378)Target is in a DefaultPool
(1106: 51.12s 258792664517us)(0x3378)Target has RENDERTARGET usage
(1107: 51.12s 258792664526us)(0x3378)Target Format is 22
(1108: 51.12s 258792664536us)(0x3378)ActiveFlags( )
(1109: 51.12s 258792664545us)(0x3378)Source name is clbkCreateSurface Handle=0x4DFCA50 (154,6)
(1110: 51.12s 258792664555us)(0x3378)Source Has a Surface Interface
(1111: 51.12s 258792664564us)(0x3378)Source is in a SystemMemPool
(1112: 51.12s 258792664574us)(0x3378)Source is a PLAIN surface
(1113: 51.12s 258792664583us)(0x3378)Source Format is 22
(1114: 51.12s 258792664592us)(0x3378)ActiveFlags( )
(1115: 51.91s 258793457163us)(0x3378) --------------ExitModule------------
(1116: 51.91s 258793458788us)(0x3378) Log Closed

@Ripley: I'll give it a shot, thanks!

@Ripley & Kuddel: The update to version 16.5 seems to solve the problem. I can now empty the airlock without CTD! So - thanks!
But perhaps it's interesting to know what causes the crash?

For other users with the same problem (and for my future me) I'll attach v16.5 here.

View attachment D3D9ClientR16_5.zip

Thanks again!
 
Last edited:

kuddel

Donator
Donator
Joined
Apr 1, 2008
Messages
2,064
Reaction score
507
Points
113
Thanks for the information Koloss
But perhaps it's interesting to know what causes the crash?
I don't think I will put very much effort into it (as the current D3D9Client release seems to fix it), but maybe I'll find some time to look into it.
What is puzzling me is the name of the Source- & Target-surfaces... "clbkCreateSurface" isn't anything I would have expected there :shrug:
Maybe Jarmo can give a more precise answer later.

Anyway, don't expect too many analysis results soon
/Kuddel
 

jarmonik

Well-known member
Orbiter Contributor
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,651
Reaction score
785
Points
128
The CTD was caused by rectangles being outside of the surface. Both reported issues were fixed a year ago.

What is puzzling me is the name of the Source- & Target-surfaces... "clbkCreateSurface" isn't anything I would have expected there

Only a surfaces derived from a textures has names. Other's are using the name of the function that created the surface.
 
Top