Jump to content
The simFlight Network Forums

FSUIPC4 LOG ERRORS


Recommended Posts

52 minutes ago, bassgeo said:

Hello Peter, can you please check my FSUIPC4.LOG file?

Please, in future, at least state why you are attaching a file. It would be much better to just paste the contents into your message. I don't like just downloading files for the sake of it.

It looks like you are running some program interfacing to FSUIPC and writing to offsets reserved for WideClient running a Lua plug-in using the display library to get a display on the FS screen. If bad data is written to these it is quite possible to generate Access Violations, in this case probably in the depths of the display code in the Sim or its system DLL. It is to avoid crashing the Sim altogether in such cases that FSUIPC traps such crashes in the first place, logging them instead.

So, as with any reports or questions about FSUIPC or problems, more information is obviously needed. What programs are you running? Are you using WideFS? What plug-ins are you using, both in FSUIPC and the WideClients?

Please always provide at least basic information.

Pete

 

 

Link to comment
Share on other sites

Hi Peter,
Sorry for the attached file, didn't think you would mind.

I'm using WideFS with "VAS_Monitor WideFS.lua" and "VAS_Monitor.lua".

Here is my WideClient-w10.ini:

[Config]
ServerIPAddr=192.168.0.40
;ServerName=PANOSWIN10
Protocol=TCP
;Protocol=UDP
Port=8002
Window=290,573,128,64
Visible=Yes
ButtonScanInterval=20
ClassInstance=0
NetworkTiming=5,1
MailslotTiming=2000,1000
PollInterval=2000
Port2=9002
ResponseTime=18
ApplicationDelay=0
TCPcoalesce=No
WaitForNewData=500
MaxSendQ=100
OnMaxSendQ=Log
NewSendScanTime=50
Priority=3,1,2
ReconnectMinutes=0

; -----------------------------------------------
[User]
ButtonScreen=No
Log=Errors+
[ButtonScreen]
Size=4,5
 
0=T"Pause"
1=T"Slew"
2=B"Clear\rWeather"
3=B"Toggle\rTraffic"
 
4=B"Refresh\rScenery"
5=Ba"ESCape"
6=Bt"Cursor\rUp"
7=Ba"Home"
 
8=B"Reload\rAircraft"
9=Bl"Cursor\rLeft"
10=B"Stop/Clr\r(Num 5)"
11=Br"Cursor\rRight"
 
12=B"Restart\rFlight"
13=Ba"ALT\r(to get to\rFS menus)"
14=Bb"Cursor\rDown"
15=Ba"End"
 
16=B"Return"
17=B"Space\rBar"
; ===============================================
[Sounds]
Path=c:\WideFsX\Sound\
Device1=Primary Sound Driver
;Device2=SB Live! Wave Device

; ===============================================
;[GPSout]
;Port=COM6
;Speed=9600
[ExtWindow]
VAS Monitor=[0,100,523,100]
WX Radar: Range  60nm, Tilt  0.0, Opts: Nml Pch Uni=[87,391,600,300]

WX Radar: Range  0nm, Tilt  0.0, Opts: Nml Pch Uni=[726,755,600,300]
WX Radar=[607,615,600,300]


Here is my WideClient-w10.log:

********* WideClient Log [version 6.999z2] Class=FS98MAIN *********
Date (dmy): 05/04/17, Time 23:11:41.484: Client name is PIII500
      401 Attempting to connect now
      401 Trying TCP/IP addr 192.168.0.40, port 8002 ...
      401 LUA: "C:\WideFsX\Initial.LUA": not found
      411 Connection made okay!
  2674386 Timed out response: connection assumed lost!
  2674386 Ready to try connection again
  2674436 Timed out response: connection assumed lost!
  2675397 Attempting to connect now
  2675397 Trying TCP/IP addr 192.168.0.40, port 8002 ...
  2675397 Connection made okay!
  2675427 Received shutdown offset code = ADBC
  2675427 FS closing down (param=ADBC), disconnecting

  2675427 ********* Interim performance summary *********
  2675427 Total time connected so far = 2675 seconds
  2675427 Reception maximum so far:  29 frames/sec, 1512 bytes/sec
  2675427 Reception average whilst connected so far:  23 frames/sec, 1238 bytes/sec
  2675427 Transmission maximum so far:  5 frames/sec, 381 bytes/sec
  2675427 Transmission average whilst connected so far:  4 frames/sec, 293 bytes/sec
  2675427 Max receive buffer = 344, Max send depth = 4, Send frames lost = 0
  2675427 ***********************************************
  2675507 Received shutdown offset code = ADBC
  2682247 Connection closed by server!
  2682247 Attempting to connect now
  2703187 Error on client pre-Connection Select() [Error=10060] Connection timed out
  2703187 Ready to try connection again
  2704219 Attempting to connect now
  2748232 Trying TCP/IP addr 192.168.0.40, port 8002 ...

  2793106 ****** End of session performance summary ******
  2793106 Total time connected = 2675 seconds
  2793106 Reception maximum:  29 frames/sec, 1512 bytes/sec
  2793106 Reception average whilst connected:  23 frames/sec, 1238 bytes/sec
  2793106 Transmission maximum:  5 frames/sec, 381 bytes/sec
  2793106 Transmission average whilst connected:  4 frames/sec, 293 bytes/sec
  2793106 Max receive buffer = 344, Max send depth = 4, Send frames lost = 0

  2793106 ********* Log file closed (Buffers: MaxUsed 5, Alloc 165867 Freed 165867 Refused 0) *********

And my FSUIPC4.INI

[General]
UpdatedByVersion=4964f
History=ZHFJNR5X8DOSU5GYZOH25
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
NewDeleteVehiclesForAES=No
AutoScanDevices=Yes
AssignJoystickIDs=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
OOMcheck=Yes
OOMcheckInterval=10
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=10
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.4.22.19868
SimConnectUsed=3.4.0.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=Yes
Port=COM1
Speed=9600
Interval=500
PosTo6Decimal=Yes
SimModeIndicator=No
Sentences=RMA,RMC,GGA

[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=500
PosTo6Decimal=No
SimModeIndicator=No
Sentences=

[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[Sounds]
Path=C:\Prepar3D v3\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=Line 1/2 (M-Audio Delta 66)
Device4=Multichannel (M-Audio Delta 66)
Device5=S/PDIF (M-Audio Delta 66)
Device6=Line 3/4 (M-Audio Delta 66)
Device7=Realtek Digital Output (Realtek High Definition Audio)

[ClientNames]
1=PIII500

Thank you in advance for your time,

Panos

Link to comment
Share on other sites

3 hours ago, bassgeo said:

I'm using WideFS with "VAS_Monitor WideFS.lua" and "VAS_Monitor.lua".

For the same displays on both the Client and main FS screen? Why both on WideFS? For the latter it would be much more efficient to run VAS Monitor on the FS PC. 

It's late here, but I'll check this tomorrow. Do you get any of the VAS Monitor display on the P3D screen? I know there's a delay between this

   694328 Advanced Weather Interface Enabled

and the first error: 

  1579063 ***ERROR C0000005 at 58257656 ExWriteStateData(Offset=9BFC, Size=4)

That's nearly 90 seconds. Is that all WideClient start up time, before it is running the Lia plug-ins?

Perhaps you could enable ipc Write logging in FSUIPC's logging tab. That will show me exactly what it received up to the crash.

Pete

 

Link to comment
Share on other sites

9 hours ago, Pete Dowson said:

 

 

For the same displays on both the Client and main FS screen? = Only on my networked Client PC

Why both on WideFS? = I remove the "VAS_Monitor.lua" = But the errors are always there!

For the latter it would be much more efficient to run VAS Monitor on the FS PC.= I will add this string in FSUIPC4.ini:

[Monitor]
Monitor0=0,024C,4,0

It's late here, but I'll check this tomorrow. Do you get any of the VAS Monitor display on the P3D screen?= No.

   694328 Advanced Weather Interface Enabled

and the first error: 

  1579063 ***ERROR C0000005 at 58257656 ExWriteStateData(Offset=9BFC, Size=4)

That's nearly 90 seconds. Is that all WideClient start up time, before it is running the Lia plug-ins?= No delay...a few seconds only.

Perhaps you could enable ipc Write logging in FSUIPC's logging tab. That will show me exactly what it received up to the crash.= I will do!

Link to comment
Share on other sites

9 minutes ago, bassgeo said:

I remove the "VAS_Monitor.lua" = But the errors are always there!

Hmm. That's odd. Something else is writing those entries then, from a WideFS client. We'll need to do a process of elimination on whatever is running on the clients (though it could equally be something on the main sim PC -- those offsets are supposed to be for WideClient only, but anything can write there -- weith possibly the results you are getting, because they instigate calls into the sims inner code to get a display on screen).

I need the log with the ipcWrites enabled please, at least the first parts where it starts happening, until it repeats. 

In order to get that log option going when FSUIPC starts, you'll need to enable it then restart the sim.

15 minutes ago, bassgeo said:

No delay...a few seconds only.

1579063 (the first error) - 694328 (when the sim is ready) = 884735
which is 88.4735 seconds. I think about 20-30 seconds of that will be WideServer starting up.

Pete

 

Link to comment
Share on other sites

Here i am again!

********* FSUIPC4, Version 4.964f (13th March 2017) by Pete Dowson *********
Windows 10 Enterprise 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.4.22.19868
Reading options from "C:\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 10
Module base=537F0000
User Name=""
User Addr=""
FSUIPC4 Key is provided
WideFS7 Key is provided
        0 System time = 07/04/2017 12:57:16
       15 FLT UNC path = "\\WIN10\P3D_PLN\"
       15 ------ Module Version Check ------
       15        acontain.dll: 3.4.22.19868
       15             api.dll: 3.4.22.19868
       15        controls.dll: 3.4.22.19868
       15      fs-traffic.dll: 3.4.22.19868
       78             G3D.dll: 3.4.22.19868
       78        language.dll: 3.4.22.19868
       78            sim1.dll: 3.4.22.19868
       78        visualfx.dll: 3.4.22.19868
       78         weather.dll: 3.4.22.19868
       78          window.dll: 3.4.22.19868
       78 ----------------------------------
       78 Trying C:\Prepar3D v3\Modules\SimConnectP3D3.dll
       94 Found it: trying to connect
      125 FS UNC path = "\\WIN10\Prepar3DV3\"
      875 ---------------------- Joystick Device Scan -----------------------
      906 -------------------------------------------------------------------
     1031 LogOptions=00000000 00000001
     1031 -------------------------------------------------------------------
     1031 ------ Setting the hooks and direct calls into the simulator ------
     1031 --- CONTROLS timer memory location obtained ok
     1031 --- SIM1 Frictions access gained
     1031 --- FS Controls Table located ok
     1031 --- Installed Mouse Macro hooks ok.
     1031 --- Wind smoothing fix is installed
     1031 --- SimConnect intercept for texts and menus option is off
     1031 --- All links okay (except older global weather setting method)
     1031 -------------------------------------------------------------------
     1031 SimConnect_Open succeeded: waiting to check version okay
     1031 Trying to use SimConnect Prepar3D
     1031 Opened separate AI Traffic client okay
     8515 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0)
     8515 Initialising SimConnect data requests now
     8515 FSUIPC Menu entry added
     8609 \\WIN10\Users\PANOS\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
     8609 \\WIN10\Prepar3DV3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    95203 \\WIN10\Prepar3DV3\SimObjects\Airplanes\FSLabs A320 CFM\A320.air
   464562 Aircraft loaded: running normally now ...
   464562 User Aircraft ID 4 supplied, now being used
   468234 System time = 07/04/2017 13:05:04, Simulator time = 12:57:56 (11:57Z)
   468609 Aircraft="FSLabs A320X CFM"
   474172 Starting everything now ...
   479844 Advanced Weather Interface Enabled
   574015 Sim stopped: average frame rate for last 121 secs = 8.6 fps
   574015    Max AI traffic was 0 aircraft
   606250 LogOptions changed, now 00000000 00000005
   607265 WRITE0[0]  7B91,   1 bytes: 01                                               .
  1337140 WRITE repeated 9550 times
  1337140 WRITE0[0]  7B91,   1 bytes: 00                                               .
  1414640 WRITE repeated 983 times
  1414640 WRITE0[0]  0BC8,   2 bytes: 00 00                                            ..
  1414687 WRITE0[0]  7B91,   1 bytes: 00                                               .
  2244640 Sim stopped: average frame rate for last 1637 secs = 17.8 fps
  2244640    Max AI traffic was 0 aircraft
  5521578 Sim stopped: average frame rate for last 2781 secs = 26.7 fps
  5521578    Max AI traffic was 0 aircraft

After landing my system an P3D crash with this error: DXGI_ERROR_DEVICE HUNG http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=123093

I know is a "Out of memory" and has nothing to do with FSUIPC, but the same time my client PC has a crash to!

Thank you for your time!

Panos

Link to comment
Share on other sites

50 minutes ago, bassgeo said:

Here i am again!

With a log which shows none of the errors we are trying to debug! So what did you stop ? Were there any WideFS client programs running?

51 minutes ago, bassgeo said:

After landing my system an P3D crash with this error: DXGI_ERROR_DEVICE HUNG http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=123093

I know about that one, though I've never seen it. I don't think it is related to OOM.

Pete

 

Link to comment
Share on other sites

No errors anymore! I just removed the "VAS_Monitor.lua" from WideFs client PC!

Thank you for everything!

P.S. Was that some kind of magic?!
 

********* FSUIPC4, Version 4.964f (13th March 2017) by Pete Dowson *********
Windows 10 Enterprise 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.4.22.19868
Reading options from "C:\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 10
Module base=57330000
User Name=""
User Addr=""
FSUIPC4 Key is provided
WideFS7 Key is provided
       47 System time = 07/04/2017 16:14:48
       78 FLT UNC path = "\\WIN10\P3D_PLN\"
       78 ------ Module Version Check ------
       78        acontain.dll: 3.4.22.19868
       78             api.dll: 3.4.22.19868
       78        controls.dll: 3.4.22.19868
       78      fs-traffic.dll: 3.4.22.19868
       94             G3D.dll: 3.4.22.19868
       94        language.dll: 3.4.22.19868
       94            sim1.dll: 3.4.22.19868
       94        visualfx.dll: 3.4.22.19868
       94         weather.dll: 3.4.22.19868
       94          window.dll: 3.4.22.19868
       94 ----------------------------------
       94 Trying C:\Prepar3D v3\Modules\SimConnectP3D3.dll
      110 Found it: trying to connect
      141 FS UNC path = "\\WIN10\Prepar3DV3\"
      828 ---------------------- Joystick Device Scan -----------------------
      828 -------------------------------------------------------------------
      860 LogOptions=00000000 00000005
      860 -------------------------------------------------------------------
      860 ------ Setting the hooks and direct calls into the simulator ------
      860 --- CONTROLS timer memory location obtained ok
      875 --- SIM1 Frictions access gained
      875 --- FS Controls Table located ok
      875 --- Installed Mouse Macro hooks ok.
      875 --- Wind smoothing fix is installed
      875 --- SimConnect intercept for texts and menus option is off
      875 --- All links okay (except older global weather setting method)
      875 -------------------------------------------------------------------
      875 SimConnect_Open succeeded: waiting to check version okay
      875 Trying to use SimConnect Prepar3D
      875 Opened separate AI Traffic client okay
    19188 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0)
    19188 Initialising SimConnect data requests now
    19188 FSUIPC Menu entry added
    19313 \\WIN10\Users\user\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
    19313 \\WIN10\Prepar3DV3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
   131906 WRITE0[0]  330A,   2 bytes: 6F 64                                            od
   131922 WRITE0[0]  330A,   2 bytes: 6C 62                                            lb
   133985 \\WIN10\Prepar3DV3\SimObjects\Airplanes\FSLabs A320 CFM\A320.air
   136500 WRITE0[0]  0BC8,   2 bytes: 00 00                                            ..
   488328 Aircraft loaded: running normally now ...
   488328 User Aircraft ID 4 supplied, now being used
   489235 WRITE0[0]  0BC8,   2 bytes: FF 7F                                            ..
   497672 System time = 07/04/2017 16:23:06, Simulator time = 13:15:43 (12:15Z)
   497766 Aircraft="FSLabs A320-X OLYMPIC AIR A320X CFM"
   498953 Starting everything now ...
   503563 Advanced Weather Interface Enabled
   503860 WRITE0[0]  7B91,   1 bytes: 01                                               .
  1067906 WRITE repeated 5754 times
  1067906 WRITE0[0]  7B91,   1 bytes: 00                                               .
  1423516 Sim stopped: average frame rate for last 947 secs = 11.7 fps
  1423516    Max AI traffic was 0 aircraft
  1559313 WRITE repeated 6397 times
  1559313 WRITE0[0]  0BC8,   2 bytes: 00 00                                            ..
  1559375 WRITE0[0]  7B91,   1 bytes: 00                                               .
  5855141 Sim stopped: average frame rate for last 4420 secs = 26.9 fps
  5855141    Max AI traffic was 0 aircraft
  6604531 WRITE repeated 88224 times
  6604531 WRITE0[0]  0BC8,   2 bytes: FF 7F                                            ..
  6604610 WRITE0[0]  7B91,   1 bytes: 00                                               .
  6639125 Sim stopped: average frame rate for last 774 secs = 23.0 fps
  6639125    Max AI traffic was 0 aircraft
  6681094 === DLLStop called ...
  6681094 === Closing external processes we started ...
  6682110 === About to kill any Lua plug-ins still running ...
  6682250 === Closing global Lua thread
  6683250 === About to kill my timers ...
  6683453 === Restoring window procs ...
  6683453 === Unloading libraries ...
  6683453 === stopping other threads ...
  6683453 === ... GPSout ...
  6683578 === ... Memory checking ...
  6683578 === ... Button scanning ...
  6683688 === ... Axis scanning ...
  6683781 === Releasing joystick devices ...
  6683781 === Freeing macro memory
  6683781 === Removing any offset overrides
  6683781 === Closing all WideFS threads
  6691750 === Clearing any displays left
  6691750 === Calling SimConnect_Close ...
  6692360 === SimConnect_Close done!
  6692360 === AI slots deleted!
  6692360 === Freeing button memory ...
  6692360 === Closing my Windows ...
  6692360 === Freeing FS libraries ...
  6693360 === Closing devices ...
  6693360 === Closing the Log ... Bye Bye! ...
  6693360 System time = 07/04/2017 18:06:22, Simulator time = 14:22:17 (13:22Z)
  6693360 *** FSUIPC log file being closed
Minimum frame rate was 7.3 fps, Maximum was 29.9 fps
Minimum available memory recorded was 604Mb
Average frame rate for running time of 6140 secs = 24.1 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 1454 Allocs, 1427 Freed
********* FSUIPC Log file closed ***********

 

Link to comment
Share on other sites

55 minutes ago, bassgeo said:

No errors anymore! I just removed the "VAS_Monitor.lua" from WideFs client PC!

Thank you for everything!

P.S. Was that some kind of magic?!

No. That was the only thing that I provide which makes WideClient write to those offsets.  It should work, I don't know what's changed, but now we've isolated it I will find out and fix it.

Thanks for confirming.

Pete

 

Link to comment
Share on other sites

With your help I've now found and fixed this bug. Really it was an unlikely situation, which is why it hasn't been found before. Running a Lua plugin on a Client to display information from the server ON the server is obviously a little illogical. The non-WideFS VAS display plug-in is best run on the Server.

However, that's the reason why the bug hasn't been found before -- and it may well have affected a more logical application. So, thank you!

The fix will be included in the next FSUIPC update.

Pete

 

Link to comment
Share on other sites

33 minutes ago, bassgeo said:

Something new?! Using OpusFSI weather engine.

This is a useless report! What's the problem? The log just shows you still have IPC write logging on. Why? It'll make big logs and be no use to anyone without purpose!

There's a lot of files there. I simply don't know what you want me to do. I'm not going to peer through them trying to guess!

Pete

 

Link to comment
Share on other sites

52 minutes ago, bassgeo said:

I just report something that I never see before..no problem!

But you don't say what you haven't seen before!

52 minutes ago, bassgeo said:

I'm sorry make you upset!

Not upset at all, don't worry. I just wondered what it was about. I still am! ;-)

Pete

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.