Hi, guys,

Congrats on the 3.5 release. I bought it and enjoy the graphics so far.

One thing I'm having some difficulty with is freezing, though. The fast sex will freeze at random intervals, but what's most consistent is I can't get past jizzing in the container in the beginning of tentacle dreams. Right after I pick up the canister, it freezes, and I'm forced to use task manager to quit.

Here's my trace.txt

////////////////////////////////////////////////////////////
// X Moon Productions (c) 2012
////////////////////////////////////////////////////////////

Version: (3.5.0003)
Build: 64 bits
Release: Full
Date: 2015/07/14 16:52:31

////////////////////////////////////////////////////////////
// System
////////////////////////////////////////////////////////////

OS: Microsoft Windows 7 Ultimate |C:\Windows|\Device\Harddisk0\Partition1
Cpu: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (RAND-NEWUBERPC: 8190 Mb)
Graphics-card: NVIDIA GeForce GTX 285 (1024 Mb)
Sound-card: NVIDIA Virtual Audio Device (Wave Extensible) (WDM)

////////////////////////////////////////////////////////////
// Oculus Rift
////////////////////////////////////////////////////////////

Oculus Rift was not detected

////////////////////////////////////////////////////////////
// DirectX
////////////////////////////////////////////////////////////

DIRECTX_VERSION: 10.0

////////////////////////////////////////////////////////////
// Graphics device
////////////////////////////////////////////////////////////

D3D_VERTEX_PROCESSING: HARDWARE

D3D_ADAPTER_DESCRIPTION: NVIDIA GeForce GTX 285
D3D_ADAPTER_VERSION: 9.18.13.2723

D3DMULTISAMPLE_2_SAMPLES: 8,8
D3D_MAX_TEXTURE_BLEND_STAGES: 8
D3D_MAX_SIMULTANEOUS_TEXTURES: 8
D3D_MAX_TEXTURE_SIZE: 8192,8192
D3D_PIXELSHADER_VERSION: 3.0
D3D_VERTEXSHADER_VERSION: 3.0

////////////////////////////////////////////////////////////
// Sound devices
////////////////////////////////////////////////////////////

Device[0]: Default
Device[1]: Primary Sound Driver
Device[2]: Speakers (High Definition Audio Device)
Device[3]: Digital Audio (HDMI) (High Definition Audio Device)
Device[4]: Digital Audio (S/PDIF) (High Definition Audio Device)

////////////////////////////////////////////////////////////
// Current sound device
////////////////////////////////////////////////////////////

DeviceId: 0
DeviceName: Default
Channel[1]: SPEAKER_FRONT_LEFT
Channel[2]: SPEAKER_FRONT_RIGHT

Let me know what might fix this.

Thanks!

This issue is most likely not caused by the software.
The software however uses both the GPU and CPU intensively.

Most likely is an hardware problem like overheating of your system or an issue with the power.

@Xpadmin,
I am having s similar issue with V3.5 but I don't think its to do with overheating. My system temp doesn't go above 60c and yet I suffer random crashes with V3.5 only. I have tried V2.1 & V3 without any crashes. I also play games that use high end graphics without issue.

My Trace:
////////////////////////////////////////////////////////////
// X Moon Productions (c) 2012
////////////////////////////////////////////////////////////

Version: (3.5.0003)
Build: 64 bits
Release: Full
Date: 2015/07/15 12:34:48

////////////////////////////////////////////////////////////
// System
////////////////////////////////////////////////////////////

OS: Microsoft Windows 7 Ultimate |C:\Windows|\Device\Harddisk0\Partition2
Cpu: AMD FX(tm)-9590 Eight-Core Processor (LEEGAMING-PC: 8090 Mb)
Graphics-card: AMD Radeon (TM) R9 390X (17592186044415 Mb)
Sound-card: AMD High Definition Audio Device

////////////////////////////////////////////////////////////
// Oculus Rift
////////////////////////////////////////////////////////////

Oculus Rift was not detected

////////////////////////////////////////////////////////////
// DirectX
////////////////////////////////////////////////////////////

DIRECTX_VERSION: 10.0

////////////////////////////////////////////////////////////
// Graphics device
////////////////////////////////////////////////////////////

D3D_VERTEX_PROCESSING: HARDWARE

D3D_ADAPTER_DESCRIPTION: AMD Radeon (TM) R9 390 Series
D3D_ADAPTER_VERSION: 8.17.10.1395

D3DMULTISAMPLE_2_SAMPLES: 8,8
D3D_MAX_TEXTURE_BLEND_STAGES: 8
D3D_MAX_SIMULTANEOUS_TEXTURES: 8
D3D_MAX_TEXTURE_SIZE: 16384,16384
D3D_PIXELSHADER_VERSION: 3.0
D3D_VERTEXSHADER_VERSION: 3.0

////////////////////////////////////////////////////////////
// Sound devices
////////////////////////////////////////////////////////////

Device[0]: Default
Device[1]: Primary Sound Driver
Device[2]: 1 - CVTE TV (2- AMD High Definition Audio Device)
Device[3]: Digital Audio (S/PDIF) (High Definition Audio Device)
Device[4]: Digital Audio (S/PDIF) (High Definition Audio Device)

////////////////////////////////////////////////////////////
// Current sound device
////////////////////////////////////////////////////////////

DeviceId: 0
DeviceName: Default
Channel[1]: SPEAKER_FRONT_LEFT
Channel[2]: SPEAKER_FRONT_RIGHT

Any advice would be Great as I am really liking V3.5!

I there any error in the 'trace.txt' file after the freeze. Please send it if so.

Sorry xpadmin, when the game freezes I have to do a hard reset of my system. The trace I copied onto my post was taken right after the game froze and I had reset my system. I am sorry this is not of much help.

No problem. Do the freezes occur at any specific situation or after a specific playing duration?

Any information that may help pinpoint this issue may help.

The only pattern is it happens between 2 & 5 minutes play in fast sex and a little longer in story mode. What I am doing seems to have little effect on the time intervals before the system freezes.

Still my best guess is that it is a hardware problem.
Because we use the CPU intensively, the power supply needs to be clean and up to the job.

N.b.
I myself had similar issues with running XStoryPlayer on an older system.
After replacing the power supply, it was solved.

I'm currently using a Corsair CX750 psu. Do you think I may need a bigger psu?

@Crazywolfrider

It is hard for me to advice anyone on this. And the issue could still be caused by a software bug.

But because we did not get many reports on this (2 for now) and because the issue occurs after a some time and is not related to a specific action, my gut feeling says it could be a hardware issue.