Hi Behemothnl,

I'm sorry to hear you're having problems with the game crashing. To best identify the cause of the issue we'd like to request additional information so we can investigate.

Please have a read of our How to: Submit a Bug Ticket article and include as much information as you can from our list. In particular we'd be most interested in a DXDiag report (How To: Generate a DXDiag Report) for your system specs and and output log from the game.

Hope we can help,

Lee

Hi Drivetheory,

Thanks for those reports, great that you included logs and saves as well that will make life for us easier when we come to address this. I'll be adding it into our backlog for further action in our next pass through WFTO tickets.

Cheers,

Lee

Hi Max,

Great thanks for the replication steps. I can confirm the behaviour you're facing and you're right that is a truly esoteric feature! I had actually forgotten we put that in.

Good spot however I'll add this to our backlog for the next triage pass.

Cheers,

Lee

Hi drivetheory,

Thanks for dropping this in with us. Can you confirm a few things for me? 

• What level are you playing on?
• Did this occur after a save?
• Do you have an output log for this.
• Is this occuring in more than one level. Do you see other examples of this behaviour?

Cheers,

Lee

Hi Max,

Apologies for the delay in my response I've just got around to doing a pass through all our tickets. That said I went into the game and tested the behaviour you highlighted. From what I can tell this is working as intended.

Automatic wave spawning increments the level of each wave by one for each wave that is spawned. Therefore each wave becomes more powerful, there is no way to lock this via the tools.

What I did notice is that upon loading the save the Toybox UI does not display the level that the automatic wave spawner is using from its memory. Once the next wave is spawned the level will be corrected to this value. Is this the issue you are facing.

Cheers,

Lee

Hi Jiri,

In the Map Editor there are two versions of Unidentified Artefacts. One which is used as a script trigger and one which is a regular unidentified and randomly weighted artefact.

Can you confirm for me that you are spawning the right version of the artefact? Try spawning both versions and seeing if there is a difference between their behaviours.

Otherwise can you please provide screenshots for your script so I can see how to replicate the behaviour.

Cheers,

Lee

Please keep us informed FlyingWizard. I'm glad to hear the new driver seemingly resolved the issue but if you encounter another crash then please upload a new log and save files here.

I'll put this into our triage queue to review with our next pass for WFTO. As the crash is no longer occurring and there have been no other reports this issue is no longer considered urgent.

Cheers,

Lee