VirieoPerceptionProfiler.exe error

The place for all discussion of the Oculus Rift compatible open source 3D drivers.
Post Reply
hewsu
One Eyed Hopeful
Posts: 2
Joined: Wed Jan 22, 2014 7:56 am

VirieoPerceptionProfiler.exe error

Post by hewsu »

When I try to open a game profile in Virieo Perception 2.0 Profiler 0.0.1.1 I get a "Input string was not in correct format." error popup. Under error details I have the following:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Convert.ToDecimal(String value)
at VirieoPerceptionProfiler.FrmProfile..ctor(String _strGameExe, String _strGameName)
at VirieoPerceptionProfiler.FrmMain.EnterEditMode()
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.DataGridView.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
VirieoPerceptionProfiler
Assembly Version: 0.0.1.1
Win32 Version: 0.0.1.1
CodeBase: file:///D:/Executables/Programs/perception/bin/VirieoPerceptionProfiler.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Would anyone have any idea what this is about? It would seem like its some kind of Visual Studio debug mode or have something to do with .NET framework. I have tried uninstalling and reinstalling .NET 1.1 and 4.0. Also tried deleting and extracing the Virieo Perception files again numerous times.

The profiler was working for me earlier before I installed a few games, one of them being Skyrim.

User avatar
Neil
3D Angel Eyes (Moderator)
Posts: 6856
Joined: Wed Dec 31, 1969 6:00 pm
Which stereoscopic 3D solution do you primarily use?: S-3D desktop monitor
Contact:

Re: VirieoPerceptionProfiler.exe error

Post by Neil »

This isn't your fault. What happened in the previous release was the profiler would work, but the driver would write to the profile in a way that suddenly became incompatible and would cause these crash issues with the profiler.

This is all getting fixed in an impending release.

Regards,
Neil

hewsu
One Eyed Hopeful
Posts: 2
Joined: Wed Jan 22, 2014 7:56 am

Re: VirieoPerceptionProfiler.exe error

Post by hewsu »

Thanks for the reply! I feared I had screwed by computer with some imcompatible software combinations. Now I can keep on VR'ing with a peace of mind again! :D Hopefully a solution can be found to this, but in the meanwhile I can bypass the problem by manually adding the configurations :)

virror
Sharp Eyed Eagle!
Posts: 427
Joined: Fri Jan 18, 2013 7:13 am
Location: Gothenburg, Sweden

Re: VirieoPerceptionProfiler.exe error

Post by virror »

"impending release", sounds exciting! : D

User avatar
baggyg
Vireio Perception Developer
Vireio Perception Developer
Posts: 491
Joined: Sat May 19, 2012 5:20 am
Which stereoscopic 3D solution do you primarily use?: S-3D HDTV
Location: BB, Slovakia

Re: VirieoPerceptionProfiler.exe error

Post by baggyg »

The Profiler work is all finished and ready to go (including a fix for this).

Just waiting for the next release since it is reliant on a couple of new settings that weren't there before.

Post Reply

Return to “Development / General Discussion”