Results 1 to 4 of 4

Thread: Testing Rules; Read it!

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    apple's Avatar Searching for 42
    Join Date
    Feb 2008
    Location
    Stockholm Sweden
    Posts
    11,780

    Default Testing Rules; Read it!

    Here is a list of what you should and shouldn't do.

    You should as a beta tester always follow these rules as it makes our life's
    (the team) much easier.


    Rules:

    1: Custom Battles:
    Spoiler Alert, click show to read: 
    1. The custom battles in RS2 are fully functional for many factions, whether there are unit cards or not.
    Custom Battles can eliminate problems with units before a player ever gets to the Campaign, so it is a Beta Testers job to
    pound the crap out of Custom battles for every funtional faction!

    2. Write down what units you recruit to play, and play against, an alternative to that is to save your army composition just
    before starting the battle.

    3. If you get a CTD in a Custom battle and there is no error, there is a specific procedure for finding the culprit:

    a. Load the same faction you were playing, and the exact same units you used before, and then load only one known
    good unit from another faction. ALL of Carthage's units are perfect, so I always use one of theirs. This eliminates any
    possibility of two units causing the trouble.
    b. If it CTD's again, load one or two units at a time from the units you recruited, and test against the same Carthage or
    known good unit. No CTD, cross them off, and keep doing this until you either find the one (by process of elimination) that is
    causing the problem...or, you find nothing.
    c. In that case, it was the units from the OTHER faction, which you wrote down.
    d. Do the same thing with this faction, eliminating the good ones until you find the bad.

    4. If you get an error message, report the error message exactly as displayed. I just write them down. Screen shots aren't
    necessary but work as well.

    5. If you got an in-battle CTD during a Campaign, load the same units in Custom Battle and test them as above.


    2: Graphical & Interface Testing:
    Spoiler Alert, click show to read: 
    1. Open and click on everything, read the tool tips and reporting anything that seams wrong.
    Read unit descriptions and look for 'garbage text'....the file is just huge and I could spend hours and hours checking every line for garbage machine code. But it needs to be done.

    2. Click and right click on all buildings. Bring up dialogues and descriptions.
    If you get a CTD clicking on one, write down and report WHAT building did that. If you can't remember, restart and go back in there and do it again.

    3. Characters, General's, Family Trees, etc......look, click, move, change, otherwise mess with and torture, looking for any CTD's (usually traits in this area).
    Remember what caused it, write down and report.

    4. Check Banners, Icons, flags above cities.


    3: Save!
    Spoiler Alert, click show to read: 
    Save before every battle.
    Why? So if you get a CTD in one, you can replay it and find out what armies were involved, and EXACTLY what units were in them.


    4: Change/Alter:
    Spoiler Alert, click show to read: 
    Do not change or alter any files at your discretion, or in any way modify any file in this mod.


    5: Keep It Secret
    Spoiler Alert, click show to read: 
    Never tell, distribute or in any other way give away information/material that in anyway could compromise the mod or/and it's contributors.
    All material we provide you are property of the Roma Surrectum team.
    Last edited by apple; July 03, 2009 at 07:21 PM.
    Son of Legio
    Father of Paedric & Remlap
    Roma Surrectum II, Ages of Darkness II, Rome Total Realism & RTR: Imperium Surrectum Developer

    Mundus Bellicus - TWC - ModDB - Discord - Steam

  2. #2

    Default Re: Testing Rules; Read it!

    ....and please play any beta campaigns with Fog of War switched off (in the preferences.txt file)


    Under patronage of Spirit of Rob; Patron of Century X, Pacco, Cherryfunk, Leif Erikson.

  3. #3

    Default Re: Testing Rules; Read it!

    Also I'd suggest saving before every end of campaign turn. There is still at least one random CTD that needs to be tracked down.

    Make sure that autosave is switched off however (in preferences.txt)


    Under patronage of Spirit of Rob; Patron of Century X, Pacco, Cherryfunk, Leif Erikson.

  4. #4
    dvk901's Avatar Consummatum est
    Patrician

    Join Date
    Mar 2006
    Location
    Michigan
    Posts
    20,984

    Default Re: Testing Rules; Read it!

    Gentlemen, I'm getting really annoyed with reports that "Oh my gosh, I got a CTD and now I can't continue my campaign. What do I do?" Or, "I got the exact same CTD (as someone else)." I can release this to the general public and get that kind of feedback. As Beta testers you are REQUIRED to provide every bit of information regarding a CTD that can possibly be provided. Screenshots of conditions just before the CTD, the character's name, faction, regions, buildings, anything and everything that could have something to do with that CTD.

    Regarding campaigns you are playing....I know there have been a lot of changes and interrupted campaigns. That's the 'bain' of Beta testing. You are NOT here to play campaigns. You are here to help us test this mod, and report consistantly what's going on in your campaigns. I'm not seeing a lot of screenshots. I'm not seeing progress reports. I am seeing a lot of chatter about units and discussing stuff, but this is not helping to adjust and tweak this thing so that it plays nicely for everyone else when it's released. A few people are providing a lot of decent feedback...LEARN from them, because that is what I expect of everyone who is on this team.

    Creator of: "Ecce, Roma Surrectum....Behold, Rome Arises!"
    R.I.P. My Beloved Father

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •