Game crash - inscribe ammo w/ @f8

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Oraticus
    Apprentice
    • Sep 2014
    • 84

    Game crash - inscribe ammo w/ @f8

    Whoo! First post here on the forums!

    I was inscribing my more powerful arrows to keep them at the bottom of my munitions list, and noticed that if I inscribed the first stack with @f9, trying to inscribe the second stack with @f8, or @f7, or anything else caused my game to crash. However, if I did it the other way, inscribing the @f8 first, then the @f9, it's fine. Anyone else experienced this yet?

    Could it have anything to do with the fact that when I inscribed the @f9, the list of ammunition expands out to show f2-f7 being (nothing)? When I inscribed @f8, the list didn't expand...
    Last edited by Oraticus; November 5, 2014, 20:02.
  • Ingwe Ingweron
    Veteran
    • Jan 2009
    • 2129

    #2
    The quiver crash bug was reported often in the 3.5 dev and still persists. A crash will often occur if you inscribe ammo higher than an empty quiver slot. E.g., you have ammo {@f0=g} and {@f1=g}. You find a great Holy Might ammo and want to inscribe it high up in the quiver, so you try: {@f8=g}. Bang! The game crashes. Inscribing past those empty quiver slots 2-7 results in a game crash. Currently, to avoid the quiver crash you should inscribe ammo without leaving empty slots.

    Note, once you use up ammo in an intervening slot, that slot will be empty in the quiver. E.g., you had ammo inscribed at 0, 1, 2, and 3. If you use up all of slot 2, it will be empty. Don't try inscribing at 4 until you fill 2 back up or you risk the crash.
    “We're more of the love, blood, and rhetoric school. Well, we can do you blood and love without the rhetoric, and we can do you blood and rhetoric without the love, and we can do you all three concurrent or consecutive. But we can't give you love and rhetoric without the blood. Blood is compulsory. They're all blood, you see.”
    ― Tom Stoppard, Rosencrantz and Guildenstern are Dead

    Comment

    • MattB
      Veteran
      • Mar 2013
      • 1214

      #3
      Hi Oraticus - welcome along!

      Out of interest, are you using 3.5dev or 3.5 proper?
      I haven't had any problems with this crash since the actual (Christmas Eve) release, but maybe I just trained myself to avoid it without noticing.

      Comment

      • Oraticus
        Apprentice
        • Sep 2014
        • 84

        #4
        Thanks for the quick reply... yeah, I figured it had to be something someone had already noticed, but didn't find a thread on it.

        I'm pretty sure it was just 3.5.0... no where did I see "Dev". Whatever version is linked from the main page of http://rephial.org/.

        It seems to be fine if I inscribe them in ascending order, or at least as long as the ammo list hasn't expanded. I suppose I'll make sure to only mess with it when I arrive on a new floor so the autosave feature can do its thing just in case.
        Last edited by Oraticus; November 5, 2014, 20:02.

        Comment

        • MattB
          Veteran
          • Mar 2013
          • 1214

          #5
          Originally posted by Oraticus
          [FONT="Comic Sans MS"][COLOR="Lime"]
          I'm pretty sure it was just 3.5.0... no where did I see "Dev". Whatever version is linked from the main page of http://rephial.org/.
          Yep, that'll be the actual release then.
          Just be sure to use the '@f...' inscriptions in order. You can put more than one type of ammo at, say, @f2. What I do is put normal ammo at @f0, magic ammo at @f1 and excellent at @f2, superlative at @f3 - irrespective of how many types of magic or excellent ammo I have. That way things tend to inscribe in order.

          Comment

          • Ingwe Ingweron
            Veteran
            • Jan 2009
            • 2129

            #6
            I used to do the same, average at @f0, magical at @f1, etc. But then you need to adjust when you stop using or have used up average missiles, or you get the crash upon inscribing higher than the empty f0 slot.

            At some point, I just stopped inscribing slots and just went with =g and look at the monster info and decide which ammo to fire from there.
            “We're more of the love, blood, and rhetoric school. Well, we can do you blood and love without the rhetoric, and we can do you blood and rhetoric without the love, and we can do you all three concurrent or consecutive. But we can't give you love and rhetoric without the blood. Blood is compulsory. They're all blood, you see.”
            ― Tom Stoppard, Rosencrantz and Guildenstern are Dead

            Comment

            • takkaria
              Veteran
              • Apr 2007
              • 1951

              #7
              Originally posted by Oraticus
              Thanks for the quick reply... yeah, I figured it had to be something someone had already noticed, but didn't find a thread on it.

              I'm pretty sure it was just 3.5.0... no where did I see "Dev". Whatever version is linked from the main page of http://rephial.org/.

              It seems to be fine if I inscribe them in ascending order, or at least as long as the ammo list hasn't expanded. I suppose I'll make sure to only mess with it when I arrive on a new floor so the autosave feature can do its thing just in case.
              I can't reproduce this bug though I've been trying quite hard. Would appreciate knowing if you can reliably make it happen & what steps to take. Also, are you using Windows or another platform?
              takkaria whispers something about options. -more-

              Comment

              • Ingwe Ingweron
                Veteran
                • Jan 2009
                • 2129

                #8
                Originally posted by takkaria
                I can't reproduce this bug though I've been trying quite hard. Would appreciate knowing if you can reliably make it happen & what steps to take. Also, are you using Windows or another platform?
                I get this crash on OSX as I used to get on Windows. To reproduce the crash try this, every time you pick up ammo - wield it; inscribe it with "@f6=g", or some such where the slot is well above the filled ammo slots in the quiver. If not every time, at least quite often, you should get the game crash.
                “We're more of the love, blood, and rhetoric school. Well, we can do you blood and love without the rhetoric, and we can do you blood and rhetoric without the love, and we can do you all three concurrent or consecutive. But we can't give you love and rhetoric without the blood. Blood is compulsory. They're all blood, you see.”
                ― Tom Stoppard, Rosencrantz and Guildenstern are Dead

                Comment

                • takkaria
                  Veteran
                  • Apr 2007
                  • 1951

                  #9
                  Originally posted by Ingwe Ingweron
                  I get this crash on OSX as I used to get on Windows. To reproduce the crash try this, every time you pick up ammo - wield it; inscribe it with "@f6=g", or some such where the slot is well above the filled ammo slots in the quiver. If not every time, at least quite often, you should get the game crash.
                  OK, thanks for this, good to know it's still present and I'm not chasing after ghosts!

                  So I've tried repeatedly picking up/inscribing/firing/dropping ammo, some of which is inscribed with "@fX=g", where X is variable, but I can't make the game crash at all. Can you reproduce it more reliably than that?

                  Is the order important? Does the crash occur when you're already wielding something your quiver and you inscribe it with @fX? Or is when you wield something to it that is already inscribed?

                  Thanks for your help with this!
                  takkaria whispers something about options. -more-

                  Comment

                  • PowerWyrm
                    Prophet
                    • Apr 2008
                    • 2987

                    #10
                    I've tried anything I could think of, wasn't able to reproduce it. I guess the only way is to ask for a savefile prior to the crash and try in debug mode.
                    PWMAngband variant maintainer - check https://github.com/draconisPW/PWMAngband (or http://www.mangband.org/forum/viewforum.php?f=9) to learn more about this new variant!

                    Comment

                    • Oraticus
                      Apprentice
                      • Sep 2014
                      • 84

                      #11
                      I'm running the game in windows, and it happened on my ranger. I'll see if i can reproduce the crash, and submit a file for you.
                      Last edited by Oraticus; November 5, 2014, 20:03.

                      Comment

                      Working...
                      😀
                      😂
                      🥰
                      😘
                      🤢
                      😎
                      😞
                      😡
                      👍
                      👎