Let me be the first to say- Yay!
You rock Mr Vux :)

everything we know is wrong again \o/

un grand merci!

c'est cool!

:D

Cheers...

new tools - new horizons, thank you Mr Vux !

thank you vux vvvvery much! you are great!

i got it working, but my old dx9 nodes are not listed any more
but if i open an old patch, they are there, and they work, i can control c+v and use them,,, is this normal or i made a mistake on the installation ?

and is there a way to convert a dx11 texture into a dx9 texuture to use the old patches ?

all dx11 nodes are red for me :/

@vjc4 @colorsound : In next release you'll be able to filter normally, so you'll be able to view those nodes again.

@Stix : are nodes appearing in nodelist?

@Stix it performs much more fast in general.... look the pipet example

@geometrica: No "pipet" node except for OpenCV now, all DX11 stuff seems to be here fine. Is there a DX11 pipet?

Sorry to be dense/blind, but I cannot find it in the node13 workshop DX11 rendering techniques I zip. Am I missing it? Thanks!

Strange thing on my laptop with AMD Radeon HD 6470M: when I try to set the renderer's input pins AA Samples per pixel to > 2 or AA Quality to > 0 vvvv 'freezes' (the UI gets really really slow), and the renderer stops updating. With some difficulty because of the unresponsive UI, I am able to reset these values, and then everything goes back to normal.

Anyone else experiencing the same issue?

@ft : I changed AA for next build, so it will be easier to use (Now AA Samples per pixel is an enum, and i removed quality, since it never looked like to make any difference).

Quite decent amount of other fixes in next build, including:

• Kinect with all textures + Face Tracker
• Support for IUserInputWindow (Mouse/Keyboard state)
• DynamicBuffer nodes fix in case of nil input
• Reflect on shader if geometry layout is invalid (reports missing semantic)
• ReadBack fix on first frame
• Memory leak fix on Texture 3D
• Memory leak fix on dynamic buffer
• Texture FX does proper cleanup after finishing
• GeomFX crash fix when attached to Query
• Image shader has Force Resolution Pin (so it uses size input instead of initial texture size)
• Quad (Layer) : replicating old quad, with auto batching ))

Also now feraltic is included as submodule, so check out should build out of the box.

great news vux :)

수고하셨어요!

hi, i'm very happy about the new pack, so finally we can have dx9 and 11 with th same vvvv. I really like and appreciate your hard work ;)

the only thing i'm not able to use is the facetracking of kinect (no dx9 and no dx11).
The node becomes red after i activate rgb, depth and skeleton (but i think they are needed to facetrack).
am i doing something wrong? or it's not working ?

cheers, and big work.
was a pleasure to meet you, vux, in london some days ago :D

Guys,
where are Kinect nodes for dx11 listed by vux? I can't find them in the nodes browser.

Edit: I resolved installing Kinect SDK 1.7.

Next release on the way, still few bits to sort, but here is little teaser:

• Option for no mips on texture loader
• Some dispose issues shoud be fixed
• Full x86/x64 build, with kinect/text and vlc for each architecture.
• Cube Texture Renderer (with option for single pass/multiple pass, and of course access to cube depth buffer).
• Texture Array Renderer (cube is a bit of a special case, but render to texture array allows you to set different cameras per slices, so you can do panoramics easily for example). Same as above, access to depth as well.
• Finally fixed little quad
• Some bugfix on render states
• Preview Node fixed.
• Some other goodies, stay tuned ;)

looking forward to it

Hi this is amazing.
All my DX11 nodes are red. TTY states:

00:00:36 ERR : Exception occured during creation of plugin: Could not load file or assembly 'file:///C:\Program Files (x86)\vvvv_45beta30.2_x64\packs\DX11\nodes\plugins\VVVV.DX11.Nodes.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.
00:00:36 - : To help us track this error down, enable the ExceptionDialog via the menu or starting vvvv with /showexceptions.

Could you help please.

Thank You)

i saw that one, too. and tried somewhat fix it https://github.com/sebllll/dx11-vvvv/commit/a8f0df8e83342e6bbc7dc5a62f69728ab956e51c

should be related to this thread: assharedtexture-renderer-temptarget

Metaballs is missing dragging and dropping vvvv.dx11.nodes.dll doesn't fix it...

32

hi first of all thanks again for the great work all the time!

Just one problem. When I upgrade to the latest release all connections to quads are missing in my project.

Is it somehow avoidable so that you can smoothly migrate projects over the upcoming DX11 releases? Anyone else had this problem?

Cheers

ah okey I checked and you are right I installed b31 dx11 pack in b31.2 vvvv and replaced one day dx9 quads to dx11 quads. So there is no way around doing the same procedure again you are saying?

I keep getting an error in the TTY renderer from one of the DX11 nodes. Not really sure what is happening but this is the error:

Stacktrace:

   at VVVV.PluginInterfaces.V2.Spread`1.get_Item(Int32 index)
   at VVVV.DX11.Nodes.Renderers.Graphics.DX11VolumeRendererNode.Update(IPluginIO pin, DX11RenderContext context)
   at VVVV.DX11.Nodes.Renderers.Graphics.DX11VolumeRendererNode.Render(DX11RenderContext context)
   at VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

04:39:39 ERR : System.DivideByZeroException in VVVV.PluginInterfaces: Attempted to divide by zero.

It is logged a few times per second and also makes "ML?" blink constantly in the Perf Meter.

I am using 32.1 64bit with the latest DX11 pack release (05.12.13) and all this is happening while the rendering (using mre.mdmod 2.1) is working fine.

The problem is that its making the TTY render useless for debugging, as this error gets logged so often.

Hi,
I wanted to use DX11 videoin in b32 but it missed.
Do you know why?
Thanks
KX

seems that the 64Bit (33.3) version has a problem findig assimp.dll

hi all v4s

I got the problem with "DX9toDx11" node issue, had any one happened?

i got blink effects!!!!
http://youtu.be/KIy4xkCq0-I

thx..^^

@ujif: first try starting vvvv without dx11 pack and see if that works. then try troubleshooting#logstartup

anybody have a flat directional shader lying around? :3

With the new b33.7-x85 vs. b33x-86 pack, I am getting about half the framerate, and frequent system crashes and stacktraces when I have renderers on outputs of two graphics cards (GTX780s). With 33x, I get roughly 70fps, and 33.7 I get about 32fps. But the worst part is the hard system crashes, which can happen in minutes to hours, but almost always within 12-24 hours. While I usually get a crash, sometimes vvvv just starts getting stacktraces:

ERR : Exception caused by node during render :/1000/73/77/0/51
 ERR : SlimDX.DXGI.DXGIException in SlimDX: DXGI_ERROR_DEVICE_REMOVED: Hardware device removed. (-2005270523)
 
 Stacktrace:
    at SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
    at SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
    at SlimDX.DXGI.SwapChain..ctor(Factory factory, ComObject device, SwapChainDescription description)
    at FeralTic.DX11.Resources.DX11SwapChain..ctor(DX11RenderContext context, IntPtr handle, Format format, SampleDescription sampledesc, Int32 rate, Int32 bufferCount)
    at VVVV.DX11.Nodes.DX11RendererNode.Update(IPluginIO pin, DX11RenderContext context)
    at VVVV.DX11.Nodes.DX11RendererNode.Render(DX11RenderContext context)
    at VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)
 
  -  : Stack Trace
  -  :    at SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
    at SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
    at SlimDX.DXGI.SwapChain..ctor(Factory factory, ComObject device, SwapChainDescription description)
    at FeralTic.DX11.Resources.DX11SwapChain..ctor(DX11RenderContext context, IntPtr handle, Format format, SampleDescription sampledesc, Int32 rate, Int32 bufferCount)
    at VVVV.DX11.Nodes.DX11RendererNode.Update(IPluginIO pin, DX11RenderContext context)
    at VVVV.DX11.Nodes.DX11RendererNode.Render(DX11RenderContext context)
    at VVVV.DX11.Lib.RenderGraph.DX11DeviceRenderer.ProcessNode(DX11Node node)

This is happening in a patch that is sending one layer to six renderers, three on each graphics card, using the ViewPort node to map the displays. The above happens for each of all six renderer nodes, not just the second card.

I have updated nVidia drivers, and tried SLI on, off, and activate all displays with no change. By just changing the DX11 pack back to 33x, I do not see the problem (but then see spurious black textures from DX9->DX11 video).

If needed I can try to isolate the problem into a patch, but as it can take hours to see the problem it may take a bit.

This is a total and literal show-stopper - any help greatly appreciated!

Where can I find c++ 2012 redistributable for Assimp????
I know its a simple question, but Ive been struggling for a long time to find it.. All DX11 nodes are not working, so I hope this could solve it..

In the latest version (33.7) Text nodes are red on two systems that have never had Visual Studio installed on them, they are OK on systems that have. This is with 33.7_x86 and 34.2_x86, in all cases setup.exe is all green.

Running Dependency Walker on VVVV.DX11.Nodes.Text.dll shows two DLLs as missing: MSVCP120D.DLL and MSVCR120D.DLL. Note these are debug version of the C runtime libraries.

Looks like this package is distributed as a debug build, and should not be?

Hey there!

@vux: any chance/plan of a FrameDelay (DX11.Texture 3D) any soon? (...or any smart cheat workaround till then?)
Just started to experiment with 3D textures in shaders but fear I will be stuck until this one little guy pops out! :)

Thanks for the info!

3D text didn't make it to the last update? :(

Thanks for this great update!

Text (DX11.Geometry) isn't working for me though.
Renderer in Girlpower is black.
On Windows 10, x64, NVIDIA 1080.

added the 1.0.1 x64 pack to a clean install of beta5 and v4 wont start anymore. remove the pack and it works again.

same problem like kamanlam ㅠㅠ

hi kamanlam
you should double check, if you downloaded the right version of the pack: x86 or 64.
Also I recommend to use 7-zip for decompression.

The Cylinder (DX11.Geometry) node is not acting how I expected; I thought it would follow the behavior of the Segment node, but it only sort of does. When cycles is < 1 and > .5, it closes the edges instead of creating a wedge opening. But when cycles is < .5, the caps form the expected segment, but the edges are directly closed to each other and do not follow the cap edges.

I would expect the caps to follow the Segment behavior, and in all cases where Cycles is < 1, the cylinder faces follow the caps. The current behavior just does not seem sensical. This is with 38.1 and DX11 1.3.1.

Is there any reason why this isn't just included in the core (or at least the addonpack) these days?

@mfan and @u7angel since dx11 is not created by us, we don't own the redistribution and selling rights to it. hence we cannot include it in the official download which is sold under the vvvv licensing conditions.

however, i think if @vux would request that we do so, it would be possible. but that needs to be discussed in more detail.

any thoughts?

I believe, that vvvv license sales would have stopped around 2017, if it weren't for vux' and his dx11.
It was always weird to me, that devvvvs never truely appreciated or even properly acknowledged that fact (besides a spraypainted quad).
This had bothered me so much, that I took the opportunity to call for financial reimbursement when I was on stage last NODE. Fortunately, a few users responded, either with one-time-payments to vux, or his patreon.

But again, this relates more to the gnarly relationship between the devvvvs and vux. While devvvvs didn't hesitate to become gold sponsors of Virgile, they never seemed to even consider something similar for vux, even though their product has been heavily depending on this very contribution.

So yeah, I endorse microdee's initiative whole heartedly, and would love to see an improvement to the status quo.

@joreg

You are arguing, that you've highlighted the quality of vux' contribution, but that was never in question. My point was that you never fully acknowledged what an essential cornerstone the contribution was and is to the well-being of vvvv group.
Why would you rather bloat the "slim core" with comatose ex9 for years than just admitting that vux has been providing the gpu features that vvvv group could have but didn't.
Now, vux never asked for anything in return, but it fills me with worry that you seem to think that means he does not need anything. What happened to T.R.U.S.T.?

Now, you got much better data than anyone to check how many commercial licensees are using dx11 (from your annual surveys), so please doublecheck. But just believe me when I tell you that EX9 does not deliver enough grapic punch that would have justified buying vvvv licenses ever since Instancing, Kinect2, Particles, Noodles, etc was common place. In some cases you gave head nods to that fact (see Spout, PBR, Craftlie).
That should tell you that vvvv group did benefit in an extraordinary way; intellectually, commercially, and financially.

Before you try to lecture David, you could rather look inside his frustration. Sure, draw up your own letter to vux instead of copy and pasting it, but make tabula rasa. Find out how you can help him, maybe it is not even money he needs, but please for the love of tasty vanilla code and streamlined installs, show some earnest gratitude that this man has silently saved your beta sales for the last couple years and will continue for at least another year.

I really hope you end up with a refreshed collaboration, that does not feel like a one-way-road to many around here. Now this was a lot on the interpersonal level of the issue, so let me get back to the factual:

DX11 is the de facto standard gpu pipeline for beta (even including vl), it would only be honest and helpful for everybody if this would be reflected in the vanilla beta as well.

edit: language

@joreg thanks for your response, that was insightful

my short reaction: my point was making DX11 the vanilla rendering path in VVVV and deprecating DX9 all-together (or at least tag it as legacy) a 1.5 decades old technology, the world moved on since by a landslide, twice even! A package manager will not solve that. Especially because the community already has one, VPM, and many creators are using it for their own packs, and many times I received the feedback "this should be included in the vvvv download" (which is btw under MIT so you do whatever you want, again without any permission, just saying... :P). Sure from hindsight it might have many bad design decisions, and a terrible codebase, but it works so far, and showing some official interest for it, I might jump back onto that band-wagon. But back to the point "you can download it via package manager" != "vanilla"!!!

DX11 for vvvv implementation is under BSD license which implies: You don't need Vux's permission to do whatever you want with it, including using it without credit/association in a closed source commercial application.

After this it's just a case of "yeah but we don't wanna" in which case, I don't even comprehend how you guys imagine making money with that attitude in the coming decade???

Btw, I don't think so Vux needs any help or more grattitude, that'd be too little too late. He moved on, working for Epic now on ray-tracing in UE4, and vvvv is far-far beyond his focus already. That's why I'm also so loud with "DX11 needs to be vanilla" in the first place, because when that repo bit-rots away in the next decade, that's the end-of-life for old-school vvvv too.

For the last 2 years I've been constantly writing these long ass, ranty comments (I also did for this one and figured I will just scrap it, what's the point anyway). It's not great. I'm not doing this because I enjoy shouting at people. But please do not consider this as "ah this soviet-eastern block asshole again is doing a tantrum". There are people who feel the same frustration as me, but instead of causing a fuss (oh god not the fuss, please not the fuss :P) they simply leave without a word, and consider vvvv as a finished episode in their life. You don't get any real feedback from that kind of behavior, until too late.

If I see early signs of shit going down, you can bet, I'll cause a big and loud fuss!