What Eddie Plays

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Estie
    Veteran
    • Apr 2008
    • 2347

    Originally posted by Pete Mack
    Nitpick: I believe Wootz steel came from India. It wasn't so much a matter of smelting as suitable Vanadium fraction.
    You are probably right, it has been a while since I watched it. I do remember though that they talked about the temperature when smelting, and that the european smiths couldnt create the temperatures required for the purity displayed in the Ulfberht+ swords, whereas the eastern cultures (be it middle or far east) had developed a sophisticated oven that could.

    Edit: OK, I rewatched the whole thing because I was curious. They speculate that the vikings might have imported crucible steel from Iran, but that it might not have originated there.
    Last edited by Estie; November 12, 2016, 21:09.

    Comment

    • Bogatyr
      Knight
      • Feb 2014
      • 525

      Originally posted by Derakon
      Also, remember, there are no bad ideas when brainstorming! You too, Bogatyr, don't think I didn't notice when you poo-poo'd my 5-turns idea!
      Just saw it as another "hey let's screw mages!" idea :P.

      Comment

      • PowerDiver
        Prophet
        • Mar 2008
        • 2820

        Originally posted by Estie
        OK, I rewatched the whole thing
        If you just watched it, do you remember what made the Ulfberht+ superior at fighting people wearing chainmail? Or did I get that from some other source?

        Comment

        • Estie
          Veteran
          • Apr 2008
          • 2347

          Originally posted by PowerDiver
          If you just watched it, do you remember what made the Ulfberht+ superior at fighting people wearing chainmail? Or did I get that from some other source?
          The viking sword in general had a sharper tip than roman cavalry swords (I suppose the gladius doesnt count, being a stabbing weapon used under tower shield walls, but anyway they dont mention the gladius).
          One guy ran a test with a dummy wearing chainmail and failed to penetrate with the broader tipped roman type, but breaks open some links with the sharp tip. Other than generally better ability to hold an edge and flexibility, the +Ulfberh+t had no advantage in this regard over common viking type swords.

          (^ that is the correct spelling btw, it seems they were worried about potential replication and asked the name designer to include at least 1 capital letter and 2 special characters for extra security. Their prudence paid off - the forgers managed to get the name wrong)

          Comment

          • PowerDiver
            Prophet
            • Mar 2008
            • 2820

            Originally posted by Estie
            the +Ulfberh+t had no advantage in this regard over common viking type swords.

            (^ that is the correct spelling btw,
            Good to know. Thanks.

            Comment

            • PowerDiver
              Prophet
              • Mar 2008
              • 2820

              I've cleaned up my code a little, and made things a little easier. It is still bad alpha code. I don't have a windows machine at the moment, so source only.

              Hopefully this link will get you to shareable files. 3.a is the current stuff, eband6 is rather ancient.

              Comment

              • t4nk
                Swordsman
                • May 2016
                • 336

                Hey, I'm on level 3 and it's already better than Vanilla.

                edit: I started a new half troll priest and people in town killed me!
                Last edited by t4nk; November 26, 2016, 23:54.

                Comment

                • debo
                  Veteran
                  • Oct 2011
                  • 2402

                  If anyone wants to build+host binaries for these somewhere temporary, we could do a comp of this.
                  Glaurung, Father of the Dragons says, 'You cannot avoid the ballyhack.'

                  Comment

                  • t4nk
                    Swordsman
                    • May 2016
                    • 336

                    Originally posted by debo
                    If anyone wants to build+host binaries for these somewhere temporary, we could do a comp of this.
                    I think I'll look into compiling a Windows version of it. Of course, cross compiling Windows software from Linux is a pretty annoying procedure, so I'll need a couple of days to muster the energy to do it if anyone else wants to compile it, I suggest you do that

                    Comment

                    • debo
                      Veteran
                      • Oct 2011
                      • 2402

                      Originally posted by t4nk
                      I think I'll look into compiling a Windows version of it. Of course, cross compiling Windows software from Linux is a pretty annoying procedure, so I'll need a couple of days to muster the energy to do it if anyone else wants to compile it, I suggest you do that
                      Yeah, cross-compiling sounds like a pain in the ass that probably will just result in problems downstream anyways. Anyone windowsy or cygwinny around?

                      Thanks for the offer t4nk.
                      Glaurung, Father of the Dragons says, 'You cannot avoid the ballyhack.'

                      Comment

                      • takkaria
                        Veteran
                        • Apr 2007
                        • 1951

                        Originally posted by t4nk
                        I think I'll look into compiling a Windows version of it. Of course, cross compiling Windows software from Linux is a pretty annoying procedure, so I'll need a couple of days to muster the energy to do it if anyone else wants to compile it, I suggest you do that
                        Makefile.win already has already been set up for cross-compiing; you just need to set the $CROSS and $MINGW variables I think.
                        takkaria whispers something about options. -more-

                        Comment

                        • t4nk
                          Swordsman
                          • May 2016
                          • 336

                          Originally posted by takkaria
                          Makefile.win already has already been set up for cross-compiing; you just need to set the $CROSS and $MINGW variables I think.
                          Right, but it looks like PowerDiver never used it... it doesn't even work as written. Anyway, I compiled it:
                          Code:
                          https://mega.nz/#!JZoglRzT!kMi1DGS2AVck4370hD9GDwdgwVGw8LxtI-weEhdb814
                          Also wrote a Makefile, which (IMO) is easier to use than Makefile.win:
                          Code:
                          ttps://mega.nz/#!NQRx3LBZ!J0KnVLKWvwxM2KdgpyP8iPLDd9zjzbc3EOqWNfhNa5E
                          Some things: when you dump .prf file ('A' in options), the game has trouble reading them back, and complains about parse error in line 'Q:1:80:1:0' (that also happens on Linux). Also, Gervais tiles (specifically, the mask file) can't be opened in Windows 7 (at least not in the one that I have). They can be opened in Wine, but you probably don't want to use them anyway, considering how ancient Angband handles tiles

                          Comment

                          • PowerDiver
                            Prophet
                            • Mar 2008
                            • 2820

                            Originally posted by t4nk
                            Some things: when you dump .prf file ('A' in options), the game has trouble reading them back, and complains about parse error in line 'Q:1:80:1:0' (that also happens on Linux). Also, Gervais tiles (specifically, the mask file) can't be opened in Windows 7 (at least not in the one that I have). They can be opened in Wine, but you probably don't want to use them anyway, considering how ancient Angband handles tiles
                            First, thank you for producing a windows executable!

                            I never touched any windows specific stuff. I was partway on a path, diametrically opposed to the dev team approach, where I was removing edit files and making them code, when I quit that project. I don't think I touched prf stuff, but massive half-assed code mangling while drunk would be my guess as to the source of the problem, and if so it would probably be more effort to fix than it is worth.

                            I wrote this first as proof of concept of assorted ideas, and then changed anything I felt like to make a game I liked personally. I have my doubts how popular it will turn out to be. Basically, it's best for people who would like ironman 3.0 and would appreciate automation of a bunch of annoying details. It should also be of interest to developers who want to see a bunch of my ideas in action.

                            If by some miracle it gets popular I might worry about bugfixes relating to stuff I don't do personally, but no promises.

                            Comment

                            • t4nk
                              Swordsman
                              • May 2016
                              • 336

                              As for .prf file parse error: the processing of "Q:idx:tval:sval:y/n" lines is just commented out in process_pref_file_command() (files.c, 266).

                              edit: As for Gervais tiles, the game tries to open "mask32.bmp", but the file is actually called "mask.bmp". So you can just rename it to get Gervais tiles...

                              edit2: there are two files, and the script pkg_win (in scripts directory) just forgot to copy mask32.bmp! So that's why it works on Wine... looks like no one used this script either

                              And that's why it's annoying, debo
                              Last edited by t4nk; November 27, 2016, 19:33.

                              Comment

                              • PowerDiver
                                Prophet
                                • Mar 2008
                                • 2820

                                Originally posted by t4nk
                                As for .prf file parse error: the processing of "Q:idx:tval:sval:y/n" lines is just commented out in process_pref_file_command() (files.c, 266).
                                That looks purposeful.

                                I removed squelch_level, as I removed feelings entirely. Commenting the entire block of code appears to have been overkill.

                                It ought to be sufficient to comment out the squelch_level line, and fix the undeclared sq a few lines down, but I make no promises.

                                Comment

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