2.6.9

SA3ATF
Posts: 72
Joined: Mon Apr 10, 2017 9:42 pm
Location: Solleftea Sweden JP83PE
Contact:

Re: 2.6.9

Postby SA3ATF » Fri Nov 08, 2019 2:25 pm

Fun with a little bling bling too. Almost missing that part from KE9NS software modifications of Power SDR to old FlexRadios.

Thanks so much Richie and keep up the good job :)

Happy weekend to everyone from Sweden!
I don’t suffer from insanity, I enjoy every second of it!
User avatar
w-u-2-o
Posts: 1888
Joined: Fri Mar 10, 2017 1:47 pm

Re: 2.6.9

Postby w-u-2-o » Fri Nov 08, 2019 3:29 pm

ramdor wrote: V/I is only available on 7000/8000's, not sure if that info is available from other hardware.
It is not. Only on the 7 and 8K.

73,

Scott
User avatar
w-u-2-o
Posts: 1888
Joined: Fri Mar 10, 2017 1:47 pm

Re: 2.6.9

Postby w-u-2-o » Fri Nov 08, 2019 3:42 pm

Hi Richie,

Running 2.6.9 a3. DiretX, normal priority (and also below normal--no real difference noted).

I no longer can make the red flashing indicator appear. Before if I set the display update rate to 60FPS I would get it a lot. And I can no longer set the update rate above 60.

Did you remove the red indicator, or did you change something such that the code is much more efficient? Sorry if I missed something in the discussion.

Thanks!

Scott
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 4:27 pm

w-u-2-o wrote:Hi Richie,

Running 2.6.9 a3. DiretX, normal priority (and also below normal--no real difference noted).

I no longer can make the red flashing indicator appear. Before if I set the display update rate to 60FPS I would get it a lot. And I can no longer set the update rate above 60.

Did you remove the red indicator, or did you change something such that the code is much more efficient? Sorry if I missed something in the discussion.

Thanks!

Scott


Hi Scott, Thanks for info ref the V/I, shame that. I was also wondering if there are any temp sensors/data available.

Also, the red box. Oh yes, it is still there. I have not really mentioned improvements to the drawing code on the directX side of things, as there are always small incremental changes to be made, and it is now quite a bit quicker.

I also run from time to time the performance profilers in VS. This has helped me find areas of the code that are somewhat 'slow', or allocating loads and loads of objects causing the GC to go in overdrive.

Just an example, if you have Thetis expanded to the full width (height doesn't matter) of a 4k display, there will be 2247 X-pixels in the display area. Therefore 2247 data points returned from GetPixels. To draw the top line in the panadapter, that is 2247 line calls, and then to fill in, another 2247 line calls, so 4494 lines per frame, 60 fps, 269,640 line draws per second.

I have tested using a filled geometry vs vertical lines for the filled panadapter, vertical lines are much faster. I guess the complexity of the geometry is an issue for the fill algorithm.

Even a change from Math.Min makes a difference when you are calling it 1/4 million times a second ....

//Y = Math.Min(Y, H);
Y = Y < H ? Y : H;

All good fun :)

Richie.
ea3aqr
Posts: 43
Joined: Mon Mar 04, 2019 10:50 pm
Location: BCN

Re: 2.6.9

Postby ea3aqr » Fri Nov 08, 2019 4:35 pm

Increased CPU use in 2.6.9 a3 release?

After installing the latest release, my Thetis CPU use is about 9%. With previous releases it was always 5-6%.

Is that normal?

EDIT: Looks like something is wrong... just opening Thetis without starting the connection to the radio, the CPU use is abut 2.5-3% doing nothing
Last edited by ea3aqr on Fri Nov 08, 2019 4:40 pm, edited 1 time in total.
User avatar
w2ner
Posts: 51
Joined: Wed Sep 11, 2019 12:14 am

Re: 2.6.9

Postby w2ner » Fri Nov 08, 2019 4:37 pm

Richie

Now that I have all the issues taken care of I was having with the firmware. I'm seeing SEQ errors.. I did have it dedicated to a local NIC card but messing with getting the firmware fixed, I moved it over to the network. I recall this was the reason I moved it to the dedicated NIC. These errors mean anything to you?

DCC2
s0=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 396 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/08 11:35:10:744
s1=0 0 0 0 0 0 0 0 0 0 0 0 0 396 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/08 11:34:10:744
s2=0 0 0 0 0 0 396 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/08 11:33:10:744
s3=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 396 11/08 11:32:10:744

DCC2
s0=0 0 0 0 0 0 0 0 0 0 0 0 0 396 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/08 11:34:10:744
s1=0 0 0 0 0 0 396 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/08 11:33:10:744
s2=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 396 11/08 11:32:10:744

DCC2
s0=0 0 0 0 0 0 396 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/08 11:33:10:744
s1=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 396 11/08 11:32:10:744

DCC2
s0=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 396 11/08 11:32:10:744
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 4:42 pm

ea3aqr wrote:Increased CPU use in 2.6.9 a3 release?

After installing the latest release, my Thetis CPU use is about 9%. With previous releases it was always 5-6%.

Is that normal?


all very fluid really... big pinch of salt required, nothing has been done to perform what looks like 'a 1/3 more work'
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 4:49 pm

w2ner wrote:Richie

Now that I have all the issues taken care of I was having with the firmware. I'm seeing SEQ errors.. I did have it dedicated to a local NIC card but messing with getting the firmware fixed, I moved it over to the network. I recall this was the reason I moved it to the dedicated NIC. These errors mean anything to you?


Good news on the FW. Yep they do. The packet before 396 was the expected packet, ie, a delta of 0. However, after that packet, the next one was 396 ahead of expected, meaning that there had been a whole load lost. -ve values are the important ones to us at the moment, and as far as I can tell no one has reported any. Negative will mean that the packet arriving has a sequence number lower than expected, so completely out of order, which an implementation of PRO could potentially resolve. As you are not seeing -ve's after the 396 everything recovered and no strange sequence numbers arrived.

I too have those big packet loss numbers, but then my LAN is a hotpotch of cheap routers, underground cat5 to the shack outhouse, 100mbit, 1gbit, and 10gbit segments. I am amazed it works at all ;) I have tried everything short of altering MTU, which are larger than the 1444 max packet size that I can see in the code anyway, so no fragmentation should occur.

Richie.
NC3Z
Posts: 179
Joined: Sun Oct 29, 2017 8:57 pm
Location: Merritt, NC

Re: 2.6.9

Postby NC3Z » Fri Nov 08, 2019 4:51 pm

ramdor wrote:Just an example, if you have Thetis expanded to the full width (height doesn't matter) of a 4k display


I had been running 30FPS on my 4K monitor since you added the red dot. So seeing this post from Scott I decided to run a 60FPS again, no red dot anywhere. So then I decided to run fully screen and 60FPS on my 4K, which has always been a problem, and no red dot and all very smooth.

And this is SmartSDR running and 2 instances of WSJT-X on the same PC. This was not possible before.
Gary NC3Z
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 4:57 pm

w2ner, Nicholas, before you move over to dedicated nic, can you run the following commands in cmd window...

The first gives you a list of interfaces, use te number on the left to pass into the next command to get the data. Screen shot that, and repeat on with the dedicated NIC.

Could provide some important info. Cheers, Richie.

Capture.PNG
Capture.PNG (24.19 KiB) Viewed 941 times
User avatar
w2ner
Posts: 51
Joined: Wed Sep 11, 2019 12:14 am

Re: 2.6.9

Postby w2ner » Fri Nov 08, 2019 5:05 pm

ramdor wrote:w2ner, Nicholas, before you move over to dedicated nic, can you run the following commands in cmd window...

The first gives you a list of interfaces, use te number on the left to pass into the next command to get the data. Screen shot that, and repeat on with the dedicated NIC.

Could provide some important info. Cheers, Richie.

Capture.PNG


I'll do that today. I changed a NIC card setting and enabled "Jumbo Packets" and it seems to have fixed it. I have some things to do in the yard but I will leave the systems running and see if it logs anything. I'll post an update later today.
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 5:06 pm

ea3aqr wrote:EDIT: Looks like something is wrong... just opening Thetis without starting the connection to the radio, the CPU use is abut 2.5-3% doing nothing


set display to OFF, instead of panadaptor or something. At the moment the screen is being redrawn even if no radio connection, so you can actually pan around, zoom etc etc even without radio connected. Also, the display arrays are still iterated through. Not ideal but it is how it is atm.

Richie.
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 5:13 pm

w2ner wrote:I'll do that today. I changed a NIC card setting and enabled "Jumbo Packets" and it seems to have fixed it. I have some things to do in the yard but I will leave the systems running and see if it logs anything. I'll post an update later today.


Very interesting, I didnt change that setting when I was testing earlier in the week.
User avatar
w-u-2-o
Posts: 1888
Joined: Fri Mar 10, 2017 1:47 pm

Re: 2.6.9

Postby w-u-2-o » Fri Nov 08, 2019 5:20 pm

For your situational awareness, Bryan just started another thread dealing with seq log issues specifically. He and I are in general agreement that it can be tough to delineate between lost packets due to NIC or IP stack issues, or because of blocked threads. It would be lovely to figure out a way to find the root cause.

However, more interestingly, Bryan appears to be the first person to report negative numbers, i.e. packets out of order. So it can and does happen with Thetis as well as PowerSDR. And the numbers are low, just like expected. Therefore it may be worth adding the packet reordering code.

FWIW I've tried every setting available on my NICs and found there to be little to no difference in performance. This is most likely because on my machine I was thread schedule limited, not IP stack limited. Other may have different experiences.

BREAK

Richie: if I still was leading engineering teams I would hire you in a heartbeat. Your attention to detail is spectacular. Every little bit of extra efficiency you wring out of the code is of such great benefit because clearly this thing was running on the ragged edge before, in fact in most cases over the ragged edge. I knew there had to be good reasons why I can run 10's of audio channels in DAW software, with piles of DSP plug-in's, and not hear a single glitch, but PowerSDR and Thetis were struggling while doing far less work.

Thanks,

Scott
ea3aqr
Posts: 43
Joined: Mon Mar 04, 2019 10:50 pm
Location: BCN

Re: 2.6.9

Postby ea3aqr » Fri Nov 08, 2019 5:22 pm

ramdor wrote:
ea3aqr wrote:EDIT: Looks like something is wrong... just opening Thetis without starting the connection to the radio, the CPU use is abut 2.5-3% doing nothing


set display to OFF, instead of panadaptor or something. At the moment the screen is being redrawn even if no radio connection, so you can actually pan around, zoom etc etc even without radio connected. Also, the display arrays are still iterated through. Not ideal but it is how it is atm.

Richie.


Ok, setting display to OFF, CPU usage goes to 0%.
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 5:30 pm

ea3aqr wrote:Ok, setting display to OFF, CPU usage goes to 0%.


and if you now connect to the radio with display as OFF, that will show you the work done by everything else in Thetis other than the display, give or take ;)
User avatar
w-u-2-o
Posts: 1888
Joined: Fri Mar 10, 2017 1:47 pm

Re: 2.6.9

Postby w-u-2-o » Fri Nov 08, 2019 5:41 pm

As expected with DirectX, there is no perceptible difference in CPU consumption between display on Panafall or display off.

Seeing about 8% on 4 real cores here. Number of cores seemed to matter the last time we started comparing CPU consumption, with more cores being better, and there was no difference associated with varying sampling rates, RX2, PS, etc.
ea3aqr
Posts: 43
Joined: Mon Mar 04, 2019 10:50 pm
Location: BCN

Re: 2.6.9

Postby ea3aqr » Fri Nov 08, 2019 5:42 pm

ramdor wrote:
ea3aqr wrote:Ok, setting display to OFF, CPU usage goes to 0%.


and if you now connect to the radio with display as OFF, that will show you the work done by everything else in Thetis other than the display, give or take ;)


1) Panafall mode ON and NOT connected to radio 4.5% CPU use.
2) Display OFF and connected to radio 3.5% CPU use.
3) Panafall mode ON and connected to radio 8.5 to 8.9% CPU Use.

EDIT: 8 cores 16 threads CPU here (Ryzen 7 3700x)
ea3aqr
Posts: 43
Joined: Mon Mar 04, 2019 10:50 pm
Location: BCN

Re: 2.6.9

Postby ea3aqr » Fri Nov 08, 2019 5:48 pm

My bad! I was using GDI mode... OMG!

Switching back to Direct X my CPU usage went down again to 4-5%.

Excuse me... :oops:
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Fri Nov 08, 2019 6:44 pm

UPDATE

Hi all,

Small update that signifies the start of changes to the interface. Clock panel has been moved to a status bar, which also provides a warning triangle if any seq errors occur.

Setup->Appearance->General where you can change back and text colour of status bar.

Please try : link removed, see post #1

Cheers, Richie.

(11/3/10) a4
-add: added a status bar, and moved the clock panel over. A warning triangle will appear if there are any SEQ errors. Click triangle to bring up Seq log. Click clear in the seq log to clear the warning. Any -ve seq errors will show RED surround. RED surround is an important SEQ error, please screenshot the seq log window and report on forums if this happens.
Last edited by ramdor on Mon Nov 11, 2019 5:00 pm, edited 1 time in total.
User avatar
Tony EI7BMB
Posts: 292
Joined: Sun Apr 09, 2017 2:31 pm
Location: Dublin
Contact:

Re: 2.6.9

Postby Tony EI7BMB » Fri Nov 08, 2019 7:22 pm

installed and running, looks great

Screenshot 2019-11-08 19.25.51.png
Screenshot 2019-11-08 19.25.51.png (1.93 MiB) Viewed 898 times
User avatar
W1AEX
Posts: 250
Joined: Sun Apr 09, 2017 6:17 pm
Location: Connecticut, USA
Contact:

Re: 2.6.9

Postby W1AEX » Fri Nov 08, 2019 7:41 pm

Richie,

As someone who makes skins for Thetis and OpenHPSDR mRX PS I love the Date/Time/CPU data being moved to the new status bar. Now I can move my Collins Emblem further down into that open field so it looks better. Also, nice touch displaying the size of the window. Makes it a snap for me to re-size Thetis for my 1280 x 720 screen captures in my video capture software!

Thank you again!

Rob W1AEX

Image
"One thing I am certain of is that there is too much certainty in the world."
User avatar
w2ner
Posts: 51
Joined: Wed Sep 11, 2019 12:14 am

Re: 2.6.9

Postby w2ner » Fri Nov 08, 2019 8:14 pm

ramdor wrote:w2ner, Nicholas, before you move over to dedicated nic, can you run the following commands in cmd window...

The first gives you a list of interfaces, use te number on the left to pass into the next command to get the data. Screen shot that, and repeat on with the dedicated NIC.

Could provide some important info. Cheers, Richie.

Capture.PNG


Here ya go Richie. First one is direct and the second one is on the network.. Also, with the "Jumbo packets" enabled, I did see Seq errors again so, not much of a change. The only thing I saw was, the 396 number in the log went from that to I think 63 (forgot to get a screen shot). On direct there is no errors.
Attachments
Screen Shot 2019-11-08 at 3.10.30 PM.png
Screen Shot 2019-11-08 at 3.10.30 PM.png (192.45 KiB) Viewed 882 times
Screen Shot 2019-11-08 at 2.41.41 PM.png
Screen Shot 2019-11-08 at 2.41.41 PM.png (135.58 KiB) Viewed 882 times
User avatar
W3MMR
Posts: 49
Joined: Thu Jul 11, 2019 8:36 am
Location: Chester, PA
Contact:

Re: 2.6.9

Postby W3MMR » Sat Nov 09, 2019 12:05 am

Working Great. Thanks Richie!

Perry
W3MMR
new.PNG
new.PNG (986 KiB) Viewed 843 times
Studio "A" - Anan 200D, P2 1.8, Thetis 2.6.9, Dell XPS 8700 i7-4770k, Samsung EVO 860 SSD, Nvidia GeForce GTX1050ti, 16GB RAM, Shure SM7B, AL80BX
Studio "B" - Heath-Kit DX100, D-104, National NC-303, Hammarlund HQ-140-X
User avatar
ULTIMAX
Posts: 20
Joined: Tue Apr 11, 2017 11:16 am
Contact:

Re: 2.6.9

Postby ULTIMAX » Sat Nov 09, 2019 12:48 am

download/file.php?mode=view&id=612

Richie,

I downloaded as soon as you provided the update and I love it , don't miss the old clock thing
also I love the addiction of the color choose tab.

Awesome work my Brother

Al
N3YV
73's
Attachments
Thetis A4.jpg
Thetis A4.jpg (803.9 KiB) Viewed 840 times
Last edited by ULTIMAX on Sat Nov 09, 2019 3:47 pm, edited 1 time in total.
4z1ao
Posts: 3
Joined: Wed Apr 11, 2018 10:05 am

Re: 2.6.9

Postby 4z1ao » Sat Nov 09, 2019 10:35 am

ramdor wrote:UPDATE

Hi all,

Small update that signifies the start of changes to the interface. Clock panel has been moved to a status bar, which also provides a warning triangle if any seq errors occur.

Setup->Appearance->General where you can change back and text colour of status bar.

Please try : https://www.dropbox.com/s/i3g7y6vdrtc6w ... 4.zip?dl=0

Cheers, Richie.

Here it is on my 8 core AMD Ryzen 7 2700X CPU with 16GB DDR4 and NVIDIA 1050 TX. I am also getting some SEQ errors (attached is the SEQ Log).
Hope it's useful. BTW, on the screen it shows 24% CPU usage which is unusual. Usually it's 10-11%.
73 Isaac 4Z1AO
SEQ.docx
SEQ Log
(6.32 KiB) Downloaded 10 times
SS_2019-11-09 120657.png
Screenshot
SS_2019-11-09 120657.png (1016.3 KiB) Viewed 810 times
User avatar
Tony EI7BMB
Posts: 292
Joined: Sun Apr 09, 2017 2:31 pm
Location: Dublin
Contact:

Re: 2.6.9

Postby Tony EI7BMB » Sat Nov 09, 2019 12:53 pm

Nice background pic

ULTIMAX wrote:https://apache-labs.com/community/download/file.php?mode=view&id=612



Al
N3YV
73's
User avatar
w-u-2-o
Posts: 1888
Joined: Fri Mar 10, 2017 1:47 pm

Re: 2.6.9

Postby w-u-2-o » Sat Nov 09, 2019 3:32 pm

All: let's not discuss it here, but a quick pointer to some new 7000/8000 firmware, if you haven't seen it...

https://apache-labs.com/community/viewtopic.php?f=32&t=3192

Any subsequent, non-Thetis relevant, firmware posts in this thread will be deleted ;)
User avatar
nico
Posts: 17
Joined: Wed May 22, 2019 9:06 am

Re: 2.6.9

Postby nico » Sat Nov 09, 2019 9:41 pm

Hi

Richie thank you again for doing such fantastic work with Thetis ! I have noticed a DirectX bug that that seems to have started roughly after the drop down for Direct X was added in 2.6.8 and still seems to be an issue in 2.6.9 hence why I am raising it

Thetis will close randomly (every 10 to 20 minutes) with the following SharpDX.SharpDXException error from the application event viewer in W10

I am not getting the error if I use the GDI+ engine. I have tried setting different levels of priority from the drop down and get similar behaviour


EventData

1219336973338452262
5
CLR20r3
Not available
0
Thetis.exe
2.6.9.0
5dc5b2c7
SharpDX
4.2.0.0
c9fbc82e
13c
14
SharpDX.SharpDXException

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0CA.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC34B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC36B.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC369.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC399.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Thetis.exe_be1352acedfdcb2bcc9c6bd653fb6abad8afa6_bcb3fdb1_f25f0c20-cbdd-4c58-af84-ae0ed1a5e4fc

0
3c0d6273-e36a-4e03-beb0-334712fbaf64
268435456
0827d5b8d2188a8aa0ebf4845556a126
0

and this is the dump file info

Version=1
EventType=CLR20r3
EventTime=132177920815266612
ReportType=2
Consent=1
UploadTime=132177920822632142
ReportStatus=268435456
ReportIdentifier=fa95299f-4776-4265-b0f9-786d01de62a0
IntegratorReportIdentifier=c394e1d2-607e-4899-8e46-2f7e40cfefe3
Wow64Host=34404
Wow64Guest=332
NsAppName=Thetis.exe
OriginalFilename=Thetis.exe
AppSessionGuid=00002390-0001-0036-da30-c9a31d97d501
TargetAppId=W:0006dd647b902a6c067a7996c36dda37569200000000!00002034c94ed52a76eb53fe572749a80ac3b38e2f0f!Thetis.exe
TargetAppVer=2019//11//08:18:24:07!0!Thetis.exe
BootId=4294967295
ServiceSplit=5242972
TargetAsId=10424
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=0827d5b8d2188a8aa0ebf4845556a126
Response.BucketTable=5
Response.LegacyBucketId=1219336973338452262
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=Thetis.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=2.6.9.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=5dc5b2c7
Sig[3].Name=Problem Signature 04
Sig[3].Value=SharpDX
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.2.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=c9fbc82e
Sig[6].Name=Problem Signature 07
Sig[6].Value=13c
Sig[7].Name=Problem Signature 08
Sig[7].Value=14
Sig[8].Name=Problem Signature 09
Sig[8].Value=SharpDX.SharpDXException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18362.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=2beb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=e912
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=e912ddbe3f2150e5cb48514d40be2fb5
UI[2]=C:\Program Files (x86)\OpenHPSDR\Thetis\Thetis.exe
LoadedModule[0]=C:\Program Files (x86)\OpenHPSDR\Thetis\Thetis.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNEL32.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[6]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\System32\sechost.dll
LoadedModule[8]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[9]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[10]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[11]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[12]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[13]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[14]=C:\WINDOWS\System32\combase.dll
LoadedModule[15]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[16]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[17]=C:\WINDOWS\System32\win32u.dll
LoadedModule[18]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[19]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[20]=C:\WINDOWS\System32\USER32.dll
LoadedModule[21]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[22]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[24]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[25]=C:\WINDOWS\SYSTEM32\VCRUNTIME140_CLR0400.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\ucrtbase_clr0400.dll
LoadedModule[27]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\c7625296f6cee933f010d4fca91738db\mscorlib.ni.dll
LoadedModule[28]=C:\WINDOWS\System32\ole32.dll
LoadedModule[29]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[30]=C:\Windows\System32\HsSrv.dll
LoadedModule[31]=C:\Windows\System32\WINMM.dll
LoadedModule[32]=C:\Windows\System32\DSOUND.dll
LoadedModule[33]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[34]=C:\WINDOWS\System32\UMPDC.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\winmmbase.dll
LoadedModule[36]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[37]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\df3270451eeb6051bbc29a28294f4fca\System.ni.dll
LoadedModule[38]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\ee8a86eaf551d3a67c1ec35923f630d8\System.Drawing.ni.dll
LoadedModule[39]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\4d808698c61ee0fed8858575c3f7cb3f\System.Windows.Forms.ni.dll
LoadedModule[40]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[41]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[42]=C:\WINDOWS\System32\shell32.dll
LoadedModule[43]=C:\WINDOWS\System32\shcore.dll
LoadedModule[44]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[45]=C:\WINDOWS\System32\profapi.dll
LoadedModule[46]=C:\WINDOWS\System32\cryptsp.dll
LoadedModule[47]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\0b53cd264f2e036b42ad529f73a53bcd\System.Core.ni.dll
LoadedModule[48]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\4595311ef8ce0f0af816edfb63f950ca\System.Configuration.ni.dll
LoadedModule[49]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\83840284ba3c7e93f2fd7361df1c4ec3\System.Xml.ni.dll
LoadedModule[50]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[51]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[52]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.449_none_2e74e93c278899ad\comctl32.dll
LoadedModule[53]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Data\010e48eb009c6bb26a58978748463d84\System.Data.ni.dll
LoadedModule[54]=C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[55]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[56]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[57]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[58]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\netstandard\511c0eab22eb3f411f20ea40b0daa8a0\netstandard.ni.dll
LoadedModule[59]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[60]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.449_none_5f5fdc21821b137b\gdiplus.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\DWrite.dll
LoadedModule[62]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[63]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[64]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[65]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Numerics\8b3ac897f2741322fdd0dc8d4b4b135b\System.Numerics.ni.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[67]=C:\WINDOWS\System32\TextInputFramework.dll
LoadedModule[68]=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule[69]=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule[70]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[71]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[72]=C:\Program Files (x86)\OpenHPSDR\Thetis\wdsp.dll
LoadedModule[73]=C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[75]=C:\Program Files (x86)\OpenHPSDR\Thetis\libfftw3-3.dll
LoadedModule[76]=C:\Program Files (x86)\OpenHPSDR\Thetis\ChannelMaster.dll
LoadedModule[77]=C:\Program Files (x86)\OpenHPSDR\Thetis\PA19.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[79]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[80]=C:\WINDOWS\SYSTEM32\MMDevAPI.DLL
LoadedModule[81]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[83]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[84]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[85]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[86]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[88]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[89]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[90]=C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
LoadedModule[91]=C:\Program Files (x86)\ASIO4ALL v2\asio4all.dll
LoadedModule[92]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.18362.449_none_71d3f4435ae6e118\COMCTL32.dll
LoadedModule[93]=c:\windows\System32\cmasiop.dll
LoadedModule[94]=c:\program files (x86)\vb\voicemeeter\vbvmaux_asiodriver.dll
LoadedModule[95]=c:\program files (x86)\vb\voicemeeter\vbvmins_asiodriver.dll
LoadedModule[96]=c:\program files (x86)\vb\voicemeeter\vbvmpins_asiodriver.dll
LoadedModule[97]=c:\program files (x86)\vb\voicemeeter\vbvmvaio3_asiodriver.dll
LoadedModule[98]=c:\program files (x86)\vb\voicemeeter\vbvm_asiodriver.dll
LoadedModule[99]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Accessibility\27c70ba6c6887bc260788e26a161500c\Accessibility.ni.dll
LoadedModule[100]=C:\WINDOWS\SYSTEM32\oleacc.dll
LoadedModule[101]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll
LoadedModule[102]=C:\WINDOWS\SYSTEM32\MsftEdit.DLL
LoadedModule[103]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[106]=C:\WINDOWS\System32\DriverStore\FileRepository\nvlw.inf_amd64_0733b27aa51ce402\nvldumd.dll
LoadedModule[107]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[108]=C:\WINDOWS\System32\DriverStore\FileRepository\nvlw.inf_amd64_0733b27aa51ce402\nvwgf2um.dll
LoadedModule[109]=C:\WINDOWS\SYSTEM32\d2d1.dll
LoadedModule[110]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\perfcounter.dll
LoadedModule[111]=C:\WINDOWS\SYSTEM32\pdh.dll
LoadedModule[112]=C:\Windows\System32\BitsProxy.dll
LoadedModule[113]=C:\WINDOWS\System32\NSI.dll
LoadedModule[114]=C:\WINDOWS\SYSTEM32\rasman.dll
LoadedModule[115]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[116]=C:\WINDOWS\System32\perfos.dll
LoadedModule[117]=C:\Windows\System32\Windows.UI.dll
LoadedModule[118]=C:\Windows\System32\InputHost.dll
LoadedModule[119]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[120]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[121]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[122]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[123]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[124]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[125]=C:\WINDOWS\system32\wshbth.dll
LoadedModule[126]=C:\Windows\System32\rasadhlp.dll
LoadedModule[127]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[128]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[129]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[130]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[131]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[132]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18362
OsInfo[3].Key=ubr
OsInfo[3].Value=449
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=2057
OsInfo[7].Key=geoid
OsInfo[7].Value=242
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=104194
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.418.18362.0-11.0.155
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32680
OsInfo[19].Key=svolsz
OsInfo[19].Value=428
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.449.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=27A940E4-44EB-4AF0-985B-F87737BB2855.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Thetis
AppPath=C:\Program Files (x86)\OpenHPSDR\Thetis\Thetis.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=8FD996A1FF4B1B905B1B781E9A744693
MetadataHash=-872655915
User avatar
ramdor
Posts: 279
Joined: Wed Jul 03, 2019 3:07 pm

Re: 2.6.9

Postby ramdor » Sat Nov 09, 2019 9:58 pm

nico wrote:Hi

Richie thank you again for doing such fantastic work with Thetis ! I have noticed a DirectX bug that that seems to have started roughly after the drop down for Direct X was added in 2.6.8 and still seems to be an issue in 2.6.9 hence why I am raising it


Hi nico,

1) This has been happening since day1 directX implementation?
2) Are you using build a4?
3) Are you actively resizing the console when it closes? or does it just vanish?
4) What are your gfx card specs/model?
5) What resolution are you running at?
6) Have you monitored gpu temps?
7) GFX drivers updated?
8) If you still have the sun are are you running ExpertSDR2 at the same time?

Has this issue been seen by anyone else?

Cheers,

Richie.

Return to “Thetis”