• Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/

Rising Storm 2 Mod Contest - Round 2 Date Changes

Yoshiro

Senior Community Manager
Staff member
  • Oct 10, 2005
    14,530
    1
    4,508
    East Coast
    header.png




    A big hello to all of the Rising Storm 2: Vietnam players out there. While our plans for this year are to help grow the game into something bigger and better for all of our players, we have a few announcements we want to make before we start going into the details on what is next over the coming weeks.
    contestlogo.png




    First up, we have been impressed with the quality of maps that were delivered in the first phase of the community mapping contest. After getting feedback from several of those mappers we have decided to delay the submission and final judging of Phase 2 of the contest to give all entrants more time to polish up their work. The new dates are as follows:

    Deadline submission will be February 5th with final judging concluded by February 15th.

    We continue to encourage our community to check out the existing maps and mods here in the workshop: http://steamcommunity.com/app/418460/workshop/

    As mentioned before, there is content coming, but we aren't ready to drop details just yet. It is all in the works, with some QoL fixes coming to the Community Test Branch as soon as next week. But before we focus on that, we do want to cover an issue that many of you are experiencing - a launch crash, keeping many of you from playing. There are a couple of others in our sights as well, but this is the most immediate.

    First, we want to make sure all players understand that debugging and fixing this issue is our top priority currently. Annoyingly for everyone, this particular crash is one of those that is very hard to debug and enable us to pinpoint the root cause - not least of all, because we haven't been able to reproduce it in the office. In mid-December we added additional logging into the game to help us better find the actual code that is causing the issue.

    Now that the team is back in office, we are digging into those reports (thank you to all of those who sent in the reports via bugsplat - it really does make a difference). Those new reports will help us home in on a fix. If we need more data, we'll add additional logging and work from there. Obviously the aim is to get to a fix and deploy it as soon as we can. We may well deploy test fixes to the CTB, to enable volunteers to test it for us.
     
    Last edited: