Angband 2.9.3 display problem (which wasn't there a little while ago)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • teukros
    Rookie
    • May 2012
    • 5

    Angband 2.9.3 display problem (which wasn't there a little while ago)

    Using Angband 2.9.3 on WinXP SP3.

    I was playing a character, off and on, up until last September. Then real life intruded.

    Between then and now I had a nasty malware infection (including rootkits) which I took care of, but Internet Explorer was fubar'ed and I had to delete and reinstall. Currently using IE 8.0.6001.18702. No other hardware or software changes.

    No problems as of september. But when I tried to run it last night the image was all screwed up. I tried several things, figured the file was somehow corrupted, deleted it, started a new game, had the same problem, deleted the entire folder*, redownloaded from an archive, installed into a different location with a different folder name and started a new game etc. Same problem:



    That's the town level btw.

    I am satisfied that the problem is not with the save or with the executable, but something about my WinXP system which has changed since last September. But what could that be?


    *in this example I am running the 10x20 font. Now when I try to delete the folder a popup appears and informs me thusly:

    "Cannot delete 10x20.fon: Access is denied.
    "Make sure the disk is not full or write-protected and that the file is not currently in use"

    Nothing obvious shows up in Windows Task Manager | Processes. Rebooting into safe mode allows me to delete the folder, though.


    Can someone please help me with this?
  • takkaria
    Veteran
    • Apr 2007
    • 1951

    #2
    Fonts are a bit messed up in Angband 2.9.3. But if you comment out the lines to do with floor tiles in lib/pref/pref-win.prf (using # at the beginning of the line), your problem should go away. The reason you can't do anything with font files after running Angband until after a system restart is that Angband doesn't tell Windows it's finished using them properly.
    takkaria whispers something about options. -more-

    Comment

    • Pete Mack
      Prophet
      • Apr 2007
      • 6883

      #3
      You're kind of out of luck on this--2.9 was last updated 2001.
      If you want a compatible version, I recommend trying angband 3.0.6. It is the oldest one that is known to work for sure on XP.

      Edit: what Takkaria said. I am soo wrong! (Later versions do treat fonts correctly.)

      Comment

      • teukros
        Rookie
        • May 2012
        • 5

        #4
        Originally posted by takkaria
        if you comment out the lines to do with floor tiles in lib/pref/pref-win.prf (using # at the beginning of the line), your problem should go away.
        Oh yes, the floor tiles used to show up as '.' when illuminated, now they are just blank.

        So I looked at pref-win.prf and I saw this:

        # The "main-win.prf" file may actually send the "ascii" equivalent of some
        # keypad keys after the keypad key itself, especially if "numlock" is down,
        # which may cause problems. Or it may not, it is hard to tell. This is bad.

        nice

        but I am afraid that I am clueless, when looking for "lines to do with floor tiles" I see lines that look like this:

        A:\a
        P:^_Sx37\r

        A:\a\\.7
        P:^_Sx47\r

        A:\a\\.8
        P:^_Sx48\r

        A:\a\\.9
        P:^_Sx49\r

        A:\a
        P:^_Sx4A\r


        and I am afraid that I really have no idea what needs to be commented out.

        Comment

        • Nick
          Vanilla maintainer
          • Apr 2007
          • 9637

          #5
          I think it's actually font-win.prf you need to look at; where it has
          Code:
          # Floors (white / centered dot)
          
          F:1:1/31
          you want to put a # in front of the F: line.
          One for the Dark Lord on his dark throne
          In the Land of Mordor where the Shadows lie.

          Comment

          • teukros
            Rookie
            • May 2012
            • 5

            #6
            It seems to work



            Wooo HOOO



            THANK YOU!!!

            And I have an archive from December so my 27th level priest is fine. No harm, no foul.

            But what could have caused this in the first place...

            Comment

            • Derakon
              Prophet
              • Dec 2009
              • 9022

              #7
              I'm curious -- is there any particular reason why you're playing 2.9.3? Something about the newer versions that you don't like?

              Glad you got it working again, in any case!

              Comment

              • teukros
                Rookie
                • May 2012
                • 5

                #8
                I remember when 3.0.6 (I think) came out, I was horrified at the rechargeable rods... but I don't know... I guess I'm just an old stick in the mud

                Comment

                • Derakon
                  Prophet
                  • Dec 2009
                  • 9022

                  #9
                  Hey, fair enough; play the game you like! That's how we keep justify being able to make changes -- the old versions are still available so if you don't like the changes, then you don't have to play the latest version. It is helpful to know what people don't like though, hence I asked.

                  Comment

                  • Pete Mack
                    Prophet
                    • Apr 2007
                    • 6883

                    #10
                    Originally posted by teukros
                    I remember when 3.0.6 (I think) came out, I was horrified at the rechargeable rods... but I don't know... I guess I'm just an old stick in the mud
                    I don't actually think people recharge rods, except possibly vs Morgoth. The cost of breakage is just too high.

                    Comment

                    • Timo Pietilä
                      Prophet
                      • Apr 2007
                      • 4096

                      #11
                      Originally posted by Pete Mack
                      I don't actually think people recharge rods, except possibly vs Morgoth. The cost of breakage is just too high.
                      IIRC they used to be invulnerable to breakage, even from recharging, failed recharge just drained them so that it took a long time for them to recover.

                      Now they can't be recharged AFAIK.

                      Comment

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