SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and iOS Chart & Android Chart Components

0
0

Hi,
I am evaluating Scichart for high speed real time application. According to ‘Performance tips and tricks’, I enabled VisualXcceleratorEngine in my ScichartSurface. My application was working pretty well when I was using Scichart version 6.0. But when I upgraded it to Scichart version 6.1, my application was crashed every time I run it. I have to disable DirectX engine to run my application.

It seems there is a problem with this file:
..\AppData\Local\SciChart\Dependencies\v6.1.1.13136\x86\VXccelEngine2D.dll

Any thought here?

Version
6.1
  • You must to post comments
0
0

Hi Maryam

When reporting errors, could you report the error message and stack trace? This will help us to offer advice and diagnose problems.

Regarding DirectX, we are actively working on issues that affect customers with dual graphics cards, or with video cards with low video memory. Can you spend some time to run this GpuCompatibility Tool and post the results here?

SciChart GPU Compatibility Tester Tool
https://github.com/ABTSoftware/SciChart.GpuCapabilityTest

This will tell us if your video card is compatible and may offer us some clues on how we can help.

Best regards,
Andrew

  • Jean-Charles DURAND
    Hi, I have the same issue on my side. I am currently trying scichart in our real time plot application and I have one issue when I try to enable Visual Xccelerator Engine. When I run examples application or a simple prototype application, I have no issue. But when I try to enable it in my software I have an exception at control initialization coming from SciChart.Data.dll : System.AccessViolationException: ‘Attempted to read or write protected memory. This is often an indication that other memory is corrupt.’ I have the same result when I try to enable it in xaml or in code behind. Here is the stack trace: SciChart.Data.dll!SciChart.Charting2D.Interop.SCRTWPFInterop.TwisterInitEngine(uint multiSampleAntiAliasing, bool _bUseDirectX9, bool _bD3D11UseLowerFeaturesLevel, string _callbacksClassName) Unknown SciChart.Drawing.dll!SciChart.Drawing.VisualXcceleratorRasterizer.VisualXcceleratorRenderSurface.usc(bool dvg) Unknown SciChart.Drawing.dll!SciChart.Drawing.VisualXcceleratorRasterizer.VisualXcceleratorRenderSurface.VisualXcceleratorRenderSurface(SciChart.Drawing.VisualXcceleratorRasterizer.VxRenderSettings renderSettings) Unknown SciChart.Charting.dll!SciChart.Charting.VisualXcceleratorEngine.dkx(System.Windows.DependencyObject t, System.Windows.DependencyPropertyChangedEventArgs u) Unknown WindowsBase.dll!System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs e) Unknown PresentationFramework.dll!System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs e) Unknown WindowsBase.dll!System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs args) Unknown WindowsBase.dll!System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex entryIndex, System.Windows.DependencyProperty dp, System.Windows.PropertyMetadata metadata, System.Windows.EffectiveValueEntry oldEntry, ref System.Windows.EffectiveValueEntry newEntry, bool coerceWithDeferredReference, bool coerceWithCurrentValue, System.Windows.OperationType operationType) Unknown WindowsBase.dll!System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty dp, object value, System.Windows.PropertyMetadata metadata, bool coerceWithDeferredReference, bool coerceWithCurrentValue, System.Windows.OperationType operationType, bool isInternal) Unknown PresentationFramework.dll!System.Windows.Baml2006.WpfMemberInvoker.SetValue(object instance, object value) Unknown System.Xaml.dll!MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(object inst, System.Xaml.XamlMember property, object value) Unknown System.Xaml.dll!System.Xaml.XamlObjectWriter.Logic_ApplyPropertyValue(MS.Internal.Xaml.Context.ObjectWriterContext ctx, System.Xaml.XamlMember prop, object value, bool onParent) Unknown System.Xaml.dll!System.Xaml.XamlObjectWriter.Logic_DoAssignmentToParentProperty(MS.Internal.Xaml.Context.ObjectWriterContext ctx) Unknown System.Xaml.dll!System.Xaml.XamlObjectWriter.WriteEndMember() Unknown PresentationFramework.dll!System.Windows.Markup.WpfXamlLoader.TransformNodes(System.Xaml.XamlReader xamlReader, System.Xaml.XamlObjectWriter xamlWriter, bool onlyLoadOneNode, bool skipJournaledProperties, bool shouldPassLineNumberInfo, System.Xaml.IXamlLineInfo xamlLineInfo, System.Xaml.IXamlLineInfoConsumer xamlLineInfoConsumer, MS.Internal.Xaml.Context.XamlContextStack stack, System.Windows.Markup.IStyleConnector styleConnector) Unknown PresentationFramework.dll!System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader xamlReader, System.Xaml.IXamlObjectWriterFactory writerFactory, bool skipJournaledProperties, object rootObject, System.Xaml.XamlObjectWriterSettings settings, System.Uri baseUri) Unknown PresentationFramework.dll!System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader xamlReader, bool skipJournaledProperties, object rootObject, System.Xaml.Permissions.XamlAccessLevel accessLevel, System.Uri baseUri) Unknown PresentationFramework.dll!System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream stream, System.Windows.Markup.ParserContext parserContext, object parent, bool closeStream) Unknown > RSI.IndissPlus.Plots.dll!RSI.IndissPlus.Plots.SC.Toto.InitializeComponent() Line 1 C# RSI.IndissPlus.Plots.dll!RSI.IndissPlus.Plots.SC.Toto.Toto() Line 32 C#
  • Andrew Burnett-Thompson
    Hey Jean Charles, thank you for that. We’re working on an issue which affects customers with certain graphics cards, and I think we’ve fixed this issue already. Could you do me a favour and contact support [at] scichart.com? We will take steps to analyse the issue and propose a solution. Please mention in the subject line of email “AccessViolationIssue” and this forum post link. Best regards, Andrew
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.