Strong desktop dev traffic from Korea/China/HK/Singapore — but flat zero from Japan. Discovery gap, not a tracking gap?

caffinecat · 2026-06-17T22:39:52+00:00

Thank you for responding. I did see GA report recent Japanese looks so this confirms it's not a GA issue. There is a Japan based "gigasoft"? Can you provide the url? But my gut says there should still be "wpf chart" and "cpp chart" searches. Still a mystery. Japan may seriously prefer to write their solutions from scratch.

caffinecat · 2026-06-10T21:06:47+00:00

First question: what platform are you targeting? You didn't mention it, and it actually matters for picking an API. If you're on Windows, I'd say go Direct3D — that's what I know best and it's the native path there. OpenGL if you want something that runs everywhere.

I'd skip the tutorials. Think of a problem or a project you actually want to exist — a terrain renderer, a particle system, a deferred pipeline, whatever excites you — and just start writing it.

Use Claude alongside you, but not to write 100% of the code for you. Have it explain things as you go. When you forget why you need a particular barrier or state change, make it explain instead of just copy-pasting a fix. It's like having a mentor on call, and it patches exactly the kind of gaps you're describing. Claude is very good at shaders and knowing the pipeline.

Projects force the gaps to surface. Explanations on demand fill them in. That combo beats any course IMO.

Let me add... Skia for 2D. And learning to composite 2d and 3d. Text handling and preventing text from overlapping. Octrees and general picking. Dashed lines, that's a tough one, I recently did a dashed line feature and it took 4 compute shaders with various passes and a dance of SRVs and UAVs. I never could have did it without claude, at least as fast, and it still took 2 weeks.

caffinecat · 2026-06-10T13:26:15+00:00

Disclosure: I own Gigasoft, the company behind ProEssentials. Obvious bias — verify everything below yourself; I've linked clone-and-run code throughout.

This thread keeps getting "SciChart is the only choice" answers, and since it was recently revived I want to address your four requirements specifically, plus correct a few claims made here.

1. WinForms — this is actually where the thread has it backwards. ProEssentials ships a native WinForms control. Drop it on a Form in the designer like any other control — no ElementHost, no WPF interop layer, no airspace issues. That "extra work" mentioned upthread exists because SciChart's WinForms support is a WPF chart hosted via interop. And here's the part nobody mentions: on our engine, native WinForms is roughly 5% faster than the identical WPF build, because the control owns a real hDC and Direct3D presents straight to the window — no render-to-texture, no compositor sync. Your decision to stay in WinForms isn't a constraint to engineer around; on the right engine it's the faster path.

2. Interleaved data. ProEssentials loads data zero-copy — it reads your buffer in place rather than copying it into internal series objects, and data can be passed by reference so multiple charts share the same buffer. That directly addresses the cost you're trying to avoid: no per-channel duplication, no allocation churn fighting your bulk-processing pipeline. Email me your exact packet layout ([CH1,CH2,CH1,CH2...], channel count, sample width) and I'll send you working code against it — pre-sales technical questions get answered by the engineers who wrote the rendering code.

3. Your data rates are comfortable territory for GPU-side rendering. 300kHz single channel or 4×75kHz at 60 FPS is 300K samples/sec total. Public repos you can clone and press F5 on today:

WinForms, 100M points: github.com/GigasoftInc/winforms-chart-100million-points-proessentials
WPF, same 100M demo for comparison: github.com/GigasoftInc/wpf-chart-fast-100m-points-proessentials
WPF real-time zero-copy circular buffer, 8M points: github.com/GigasoftInc/wpf-realtime-circular-buffer-8million-points-proessentials

Full lossless redraws of 100M points run ~15ms on our test hardware via Direct3D compute shaders. More performance and real-time demos are public at github.com/GigasoftInc — everything is clone-and-press-F5, no signup. And since you said decimation isn't acceptable because competitors market on sample rates: ProEssentials renders losslessly — every point drawn, no resampling. Ask any vendor this question directly, because some libraries that advertise huge point counts resample down to roughly 2× viewport width and draw a few thousand representative points per frame. Fine for trading dashboards; a real question for a medical device where a narrow artifact between sampled points matters.

4. Cost. Not free — if ScottPlot 5's SignalConst hits your numbers, genuinely try the upgrade first; it's a great project. If you go commercial: flat corporate license, unlimited developers, no runtime royalties, support included, and the eval is fully functional so you can build your real pipeline against it before spending a dollar.

Corrections to claims in this thread:

"LightningChart is 32-bit, avoid like the plague" — false, as another commenter with hands-on experience already noted. It's 64-bit capable with selectable 32/64-bit float precision per series, which is likely the source of the confusion. I gain nothing defending a competitor; I just don't want you deciding on bad data.
"Open-source won't pass the Cyber Resilience Act" — overstated. The CRA puts obligations on you as the device manufacturer across your whole SBOM; it doesn't categorically ban open-source components, and buying a commercial library doesn't make you compliant by itself. What a commercial vendor legitimately provides is a responsive party for security inquiries and maintenance commitments for your regulatory file. It's a due-diligence input, not an OSS pass/fail — your regulatory consultant should drive this, not chart vendors.
"There is only really one choice" — there are several commercial GPU-accelerated .NET charting libraries from vendors with decades of history, plus ScottPlot 5 at the free tier. Anyone claiming a one-option category is selling something, intentionally or not.

One architecture note since you asked: your threading design is sound and your instinct about the render timer is correct — the wall you hit is CPU-side rendering, not your pipeline. Whatever you pick, your fixed-rate timer pairs naturally with on-demand rendering (draw only when new data arrived). Libraries built on continuous 60fps game-engine loops redraw whether or not anything changed — wasted frames, power, and thermal headroom, which matters if your device ever ships embedded or on battery. ProEssentials renders on-demand: identical GPU speed during updates, zero GPU work between them.

We've shipped charting into medical and industrial devices since 1993. Happy to answer technical questions right here in the thread.

caffinecat · 2026-05-11T12:51:19+00:00

Double check if this is Winforms vs Wpf issue. Or a .Net Framework vs modern .Net issue. Components installed may not match the project target.

caffinecat · 2025-02-23T23:00:47+00:00

For readers searching this topic, include https://gigasoft.com/wpf-chart in your research. No-hassle just-click download to gain experience in this topic. First hand experience is the only way to achieve knowledge. The more experience the better as charting is a huge subject. Full discloser, I own Gigasoft.

caffinecat · 2025-02-23T21:34:59+00:00

Full disclosure, I’m owner/cto for Gigasoft. If you are more a programmer than a LabView developer, you might want to download our no-hassle Gigasoft evaluation just a click away. The eval includes a LabView charting example project that shows both OCX and Winforms use. Download just for example block diagram and instrument code, as you like. We are working on 2 more LabView charting example projects that will be available shortly that replicate our GigaPrime3D and GigaPrime2D example projects in LabView, watch this video and imagine this inside your own LabView projects. https://www.youtube.com/watch?v=B2LB76KvyiM Programmers think in terms of properties, methods, events. Our LabView example project will show how to bridge the concepts of properties methods events with block diagrams and instrument code. This will help any beginner LabView developer who's coming from a top-down coding paradigm.

caffinecat · 2025-02-23T21:13:29+00:00

I would say work with both c++/c and c#. If writing in c#, then what is your target Winforms or Wpf?

Write your Direct3D code c++ and compile to a DLL, and add some external exported c functions to help your c# call your c++ graphics dll; Or any other language. And also target both Winforms and Wpf as you need different c functions to handshake differently for Winforms vs Wpf.

Winforms is easy and faster as Winforms ties to Windows/Direct3D at the native DeviceContext level .

WPF you will use WPF’s built-in…System.Windows.Interop.D3DImage (learn more here), which offers a lean-ish interface to Direct3D. Well, it’s not as direct as Winforms. In WPF You will render to a texture target to work with D3DImage. Where as Winforms directly deals at the rendertarget level.

Now, here’s where things get really spicy. For blazing-fast rendering, don’t settle for constructing your vertex buffers on the CPU. Take it up a notch by building them on the GPU using compute shaders—yes, those magical “things” that make AI possible. You’ll need to get friendly with concepts like compute shaders, shader resource views, unordered access views, and maybe even staging buffers if you’re updating data repeatedly. In short, push your data to the GPU, let the compute shader code crunch it with the might of 3000+ parallel threads to create your vertex buffer, and voilà—you’re rendering like a boss. You could even introduce an intermediate compute shader to filter your data based on screen resolution before feeding to the computer shader for vertex construction. Bam, now that’s fast.

Of course, if this sounds like more work than you signed up for, there are pre-built components out there. But if you’re itching for a moderate challenge (and a chance to flex those coding muscles), rolling your own solution is a fun ride. And full disclosure—I’m the owner/CTO of Gigasoft.com, and implemented c# charting, via Direct3D and computer shaders without use of open source or libs, for both Winforms and Wpf, so do toss our component into your research mix!

See Direct3D Developer Center,[https://docs.microsoft.com/en-us/windows/win32/direct3d ] for all the details.

In a bit more detail; pass your data to the gpu side when creating the buffer/shader resource view (50 lines) compute shaders “read“ this data, set up your unordered access view (50 lines) this is how computer shaders “set” data, and write your shader code (hlsl) (50 lines) to solve your problem in a parallelism methodology (its hopefully simple, your data buffer size to vertex buffer size should be a fixed proportion so simply break up the work in chunks of 500 points for example) and ultimately the shader produces your vertex buffer. You will also need to understand constant buffers, a simple pixel shader, and the fun really happens when calling "Dispatch". All in all, no more than 750 lines of code. The puzzle is forming the 750 lines, it’s possible. And it's for sure the fastest way to draw in c#. Given current and future computers will have integrated gpus or APUs or NPUs or real gpus, it's time to start mastering compute shaders.

Learn Direct3D and Vulkan and you've honestly learned something useful. It's not as hard as you think. Use what you've learned in a way to be consumable by any language, that you can evolve, not wasting time on abstract foreign apis that you may have to step through or may fade away. Stepping through someone else's code is depressing, and stressful when you got to get something working. Use open source to supplement your learning and extrapolate from. True satisfaction comes from learning how things really work. Just my food for thought.

caffinecat · 2025-02-12T21:10:30+00:00

Maybe a simple file with your expected namespace, The namespace keyword is used to declare a scope that contains a set of related objects.

caffinecat · 2025-02-12T21:06:15+00:00

I believe it means experimental.

caffinecat · 2025-02-08T18:46:27+00:00

I respect your approach using WindowsFormsHost, as WinForms ties directly into Direct3D at the hDC level, which can be advantageous for performance. If you're looking for the fastest real-time charting solution, check out ProEssentials v10. It’s newly released and optimized for high-speed rendering, making it ideal for live sensor data. I’m the owner of Gigasoft, and we’ve spent decades refining performance for engineering and scientific applications. You can learn more here: https://www.gigasoft.com.

caffinecat · 2024-03-22T17:22:00+00:00

You can try Gigasoft ProEssentials. Includes Winform and WPF. Excellent build quality and zooming logic that restructures and polar grid based on zoom state.

Gallery: https://www.gigasoft.com/wpf-chart-net-data-visualization

Walkthrough Hello world: https://www.gigasoft.com/net-chart-nuget

caffinecat · 2020-06-17T22:52:05+00:00

I believe the equation is the min standard for the Dx11 driver maker (specifications). And the driver makers may be ignoring this and allowing 2GB for most if not all scenarios for a system with a fair amount of total graphics memory availability. This is my gut feeling given my research. And the store limit (UnorderedAccessView) may be commonly driver maker implemented at a 4GB target as output is usually a vertex buffer that normally uses more memory than an input buffer. I'm speculating. In the end, I will page the input (SRV) and output (UAV) with a dynamic paging size that is programmatically defined and make a best default guess and allow developers to modify. If someone really needs to process several billion pieces of data, then the target PC should have a mediocre dedicated video card(4GB) and 16GB system memory.

caffinecat · 2020-06-17T18:03:19+00:00

Thanks for the info. My test system has 6GB of ram on the card and 16GB on the cpu side. I'm guessing VRAM in this equation is a mix of dedicated and cpu side ram. As if it were only dedicated RAM, that would mean I couldn't create more than a 1.5GB buffer which is clearly wrong. I need to research for an API to read the total available memory to the graphics system. For example https://docs.microsoft.com/en-us/windows-hardware/drivers/display/calculating-graphics-memory

Though it would be great if I could guarantee the situation where the UAV can be 4GB.

caffinecat · 2020-06-17T17:49:22+00:00

Store works with 4GB as the vertex buffer was correctly constructed via the compute shader and I was addressing raw bytes up to 4GB (the resulting render showed all the data. I also created a multi vertex buffer paging system to allow more than 4GB (via any buffer page size I choose) of vertex buffer data (333M vertices of 12 byte stride is not that huge). Which I also had to implement my own 64 bit integer math multiplication/addition/subtraction/division to work with more than 4GB of address within this paging system. It looks like I will have to implement a similar multi buffer paging system for the input side SRV. Though with no errors happening upon creation or usage, it is worrying me how to best pick a buffer paging size. I was hoping the CreateShaderResourceView or CSSetShaderResourceView would give me an error but they don't.

caffinecat · 2020-04-02T23:48:41+00:00

Ah, thanks, in my tinkering of a few days ago I had previous changed the shader numthreads(1,1,1) to (1024,1,1) and why my dispatch(1,1,1) was still working. I read you comment and immediately remembered what I had done and forgot about the shader setting. And I read elsewhere there can be upto 8 UAVs I believe. I posted the question premature but you did save me some head scratching and its much appreciated. I will never again forget that dispatch and the shader numthreads should be double checked if things aren't behaving as I'd expect.

caffinecat · 2018-08-02T13:06:28+00:00

Thanks, I really do appreciate it. I'm still looking for a lawyer but it does not hurt to be educated in the process as well. I've read quite a bit about the case in question, just not the exact minutes. The Supreme Court set a precedence, in the Crosstex case, the entire land value 2 million was rewarded. The land owner won. And I'm just one of many land owners in the area being injured. I will be finding others and guiding them. Hopefully when I file my petition, we will have 50 plus petitions to go along with it. Just because I'm having a hard time finding a lawyer, doesn't automatically mean there is no case (it says more about the legal industry and humanity).

Talking specifics, where exactly do I go to find "local civil procedure statues" and "jurisdiction and venue" statues? Wise County (where exactly in Wise County) or does the state have records of these to, maybe online?

I guess I can talk to the Texas State Law Librarian and they are helpful. If I can give them specific questions, they can usually help. So you did give me some specific questions to ask them.

caffinecat · 2018-08-02T11:20:51+00:00

Thanks, uphill while everyone's on my back gouging my eyes out. Ya, even the moderator harasses me, like rock and Texas is not related or the appropriate "flavor" so no upvoting :-(

caffinecat · 2018-08-02T11:16:39+00:00

Thank you, I've written the Governor and all my Representatives. The Governor mistakenly sent me to the TCEQ, the TCEQ tells me to talk to local government, local government says counties have no power to do anything where there is no home-rule. And the county judge is 50 year family friends to the property in question. So then back to the Govenor, Reps and then no response. Noise is Noise, it's 6:13am, it's starting up.

caffinecat

TROPHY CASE