[WiP] madVR support in MP1 (10 Viewers)

[daWooky]

If this option is unchecked, only D3D11 works.

At least that's the same for us both. just strange on insider and loves dx11
I did not make it to restore my auto3d connection and preferred to go to sleep...

dithers gradients

guess thats also why i ticked it and for what its good
thanks, i forgot its unticked by default

 

[Sebastiii]

Guys
I have a new version to test, it handle better the release on STOP for Texture and Vertex so hopping that can solve some kind of issue i have seen
V384 : http://tinyurl.com/ycjjvcxa

 

[daWooky]

new version running quite well so far
on old fse htpc and also good on 1709 and 17046 but with madvr dx11 option or windows optimisations disbled ticked for dx9 fse working.
its pretty similar like it was with v5.no errors or else seen so far with it and i successfully repaired the bravia,finally... (and btw. better never unpair a paired device in auto3d or it will be a mess^^)

 

[Sebastiii]

Great how do you fix your bravia ?
I have just seen a random error from madVR (crash) and it seems was able to fix it too (in fact the madVR windows was going quickly to my second screen but this time i was able to track down where in the code because this window was staying more longer on screen lol, lucky me )
This is nice, i'm letting running playlist over the evening, friends come tonight for diner so will see the result but looks promising already

Edit : I have added something else on stop on C# to release texture also on this side, will see the result but with this my memory leak on HTPC (few mbyte) on stop seems to be better but the result will be confirmed after few hours of running playing with 30 secs sample lol. I hope it didn't break Trakt rate dialog.

About the first fix (madVR goes to another window) will be need a new OV build, need to look the code.

Edit 2 : No need to have OV change

 

[daWooky]

sounds very good
bravia was very persistent, first the problem was that I did not know where and how the key is exactly created or can be created again .... he appears synonymous in mediaportal.xml and plugin but it does not really help to delete him there .. .addition you can create it with new auto3d but not on tv side it seemd ... so I have had a little sony remote api lesson and sadly I did not manage to start a new query to pair it really successfully again... then i did the simple solution and imaged back a bit, but still broken because the old pairing cookie isnt accepted now by the tv, also because i killed the pairing on tv side before so a even bigger sony api lesson but still no succes so i decided to used a image before i ever paired ..
but on the second time configuring auto3d again on htpc2, i had another idea or simple solution that maybe works - change tv ip manually and delete all mac and pairing cookies stuff may work...but tbh. i never want to mess with it again
wish ya a pleasant evening

 

[Sebastiii]

Here we go
V386

 

[daWooky]

normal tv usage was ok but sadly...

[2017-11-26 10:52:35,899] [Log    ] [MPMain   ] [ERROR] - Exception: Fehler in der Anwendung.
-2147467259 (E_FAIL).......

on video stop at htpc2: 1709, lav cb, mad dx 11 logs attached and my new ngu/jinc mad default settings for 1050ti

 

[Sebastiii]

@daWooky with V386 ?
Ok let's try another bin after analysing the logs

 

[daWooky]

Yep I hope so and with fse on... I just trying on windowed and it's still running

Gesendet von meinem Nexus 7 mit Tapatalk

 

[Sebastiii]

@daWooky are you able to test this one ?