FAangband 0.3.6

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Nick
    replied
    Originally posted by pampl
    I'm having trouble compiling FA for Windows. The instructions work fine for compiling V, but FA's makefile.win just throws up this error:
    Makefile.win:5: *** missing separator. Stop.
    I guess that means there's a space where a tab ought to be, but changing the formatting doesn't change the error. I tried looking through this thread to see if other people have had this problem but I didn't see anything in the last dozen or so pages, apologies if I missed it.
    I don't usually advise people not to even try, but here I will for two reasons:
    1. I have never used Makefile.win in 0.3.6 - I do my windows compiles in Linux using msys, mingw and Makefile.cyg; and (more importantly)
    2. Sometime soon (I hope within the next day or so) I will be releasing a new version, which has adopted the V build system and so should work just as for V.


    Because of this, I think my time is better spent getting the new version out the door (currently it's clinging to the door frame and I have my foot in its back) than trying to recall and understand the obsolete build system for the old version. I hope you agree, and that I don't sound too terse - if I do, it's the thought of an afternoon debugging pref file loading

    Leave a comment:


  • pampl
    replied
    I'm having trouble compiling FA for Windows. The instructions work fine for compiling V, but FA's makefile.win just throws up this error:
    Makefile.win:5: *** missing separator. Stop.
    I guess that means there's a space where a tab ought to be, but changing the formatting doesn't change the error. I tried looking through this thread to see if other people have had this problem but I didn't see anything in the last dozen or so pages, apologies if I missed it.

    Leave a comment:


  • Nick
    replied
    Originally posted by LostTemplar
    There is a bug with average weapon damage displayed by "I" command.
    Function output_dam in file info.c adds 0.0143*skill bonus damage dice in order to factor in criticals, while in attack.c file (skill/(skill+240))*2.535 average bonus dice are added (without armsman or mana burn).
    Yes, you're right; this gives an overestimate. I don't intend to do the exact calculation in info.c, but I think using
    Code:
    5 * chance + 4 * chance * 3 + 3 * chance * 12 + 2 * chance * 28
    in place of
    Code:
    5 * chance + 4 * chance * 4 + 3 * chance * 14 + 2 * chance * 40
    will give a closer estimate.

    Leave a comment:


  • LostTemplar
    replied
    There is a bug with average weapon damage displayed by "I" command.
    Function output_dam in file info.c adds 0.0143*skill bonus damage dice in order to factor in criticals, while in attack.c file (skill/(skill+240))*2.535 average bonus dice are added (without armsman or mana burn).

    Leave a comment:


  • davidk64
    replied
    CycloDS Evolution Firmware 1.54

    I tried running FAAngband DS for the first time using CyclosDS with firmware version 1.54 I have the faangband directory in the root and the faangband.nds in the root also. I get a loading message then black screens.

    Has anybody else been able to use the current version of FAAngband with CyclosDS card and latest firmware version 1.54?

    Thanks

    David

    Leave a comment:


  • Nick
    replied
    OK, I've given this a bit more thought and discussed it with some people, and here are some more ideas.

    Originally posted by Pete Mack
    How to use gestures?
    Directional movement seems like the obvious thing. Short swipe for step in a direction, long swipe for run in that direction.

    How to use inertial sensor?
    There are multiple possibilities here. My favourites are
    • Tilt to zoom - this would require intelligent use of fonts, but a little has been done toward this on the Nintendo DS port;
    • Menus are already scrollable; you could use either a scrollbar or tilt again to scroll, and then shake to select.


    How to use screen real estate?
    A small number of onscreen buttons (like the FA winCE port) and the rest map. Shake to toggle stat display on and off.

    How to avoid making errors because there's no keyboard and the screen is small?
    Make sure you can scroll and zoom. I've stuck to tilting and shaking for extra commands, but you may be able to get more than that out of the sensor.

    Leave a comment:


  • Nick
    replied
    Originally posted by Pete Mack
    iPhone doesn't have a stylus. It's fingers or nothing.
    ... and, moreover, doesn't work with a stylus, apparently. That might be a problem.

    Leave a comment:


  • Pete Mack
    replied
    Originally posted by Nick
    See the screenshots from the WinCE port in this thread. The only real issue with playability is that you might have to use a stylus rather than fingers for precision.
    iPhone doesn't have a stylus. It's fingers or nothing.

    Leave a comment:


  • Nick
    replied
    Originally posted by Pete Mack
    This is a tough port, as iPhone has no buttons. I'd like one too, but I don't have a good feel for how to write the UI.

    How to use gestures?
    How to use inertial sensor?
    These would be icing on the cake, if you could get basic functionality working.

    How to use screen real estate?
    How to avoid making errors because there's no keyboard and the screen is small?

    How to organize commands?
    What to display on the main screen?
    See the screenshots from the WinCE port in this thread. The only real issue with playability is that you might have to use a stylus rather than fingers for precision.

    Leave a comment:


  • skunker
    replied
    Originally posted by Pete Mack
    This is a tough port, as iPhone has no buttons. I'd like one too, but I don't have a good feel for how to write the UI.

    How to use gestures?
    How to use inertial sensor?
    How to use screen real estate?
    How to avoid making errors because there's no keyboard and the screen is small?

    How to organize commands?
    What to display on the main screen?

    Actually doing the port from the OSX build doesn't look so hard, as there's an old (3.0.6) Angband port to Objective C at ridiculous fish. But a straight port would be completely unplayable.
    The 3.5 Win Mobile version did a very good job of using the touch screen. Admittedly I was using a stylus so the precise touches were much easier. My old phone only had a 2.5" 320x240 screen so the iphone's screen is large in comparison. I didn't use my old slide out hardware keyboard because I played in portrait.

    I'm not a big fan of the gestures in Rogue, there are just too many and executing can be tricky. Touchscreen WinMobile phones have letter recognition which worked great when playing 2.3. Want to drop, draw a "d", zap draw a "z", etc.

    Just a thought. Of course, I probably don't need to spend anymore time playing with my phone.
    ________
    Last edited by skunker; July 12, 2022, 18:18.

    Leave a comment:


  • Nick
    replied
    Originally posted by skunker
    What are the chances an iphone version could be made?
    Well, the Rogue developer has expressed an intention to port Nethack and Angband at some point. I don't expect that I'll be doing an iPhone port any time soon, but you could always put pressure on other people (not mentioning Lebannen or Pete Mack by name).

    EDIT:Oh, hi Pete

    Leave a comment:


  • Pete Mack
    replied
    Originally posted by skunker
    What are the chances an iphone version could be made? I played the WinCE version for a good 2 years before switching. Rogue and Rogue Touch just aren't cutting it. I'm willing to donate!
    This is a tough port, as iPhone has no buttons. I'd like one too, but I don't have a good feel for how to write the UI.

    How to use gestures?
    How to use inertial sensor?
    How to use screen real estate?
    How to avoid making errors because there's no keyboard and the screen is small?

    How to organize commands?
    What to display on the main screen?

    Actually doing the port from the OSX build doesn't look so hard, as there's an old (3.0.6) Angband port to Objective C at ridiculous fish. But a straight port would be completely unplayable.

    Leave a comment:


  • skunker
    replied
    What are the chances an iphone version could be made? I played the WinCE version for a good 2 years before switching. Rogue and Rogue Touch just aren't cutting it. I'm willing to donate!
    ________
    Last edited by skunker; July 12, 2022, 18:17.

    Leave a comment:


  • Nick
    replied
    Cool - I actually do most of the V stuff already then (I've been using autotools for a while, and have a mk directory, although it looks like V has changed since I last synched at about 3.0.9). I don't have separate subdirs for win and gtk, but that shouldn't be too hard; and I'll try strategies 1 and 2 and see how I go.

    Leave a comment:


  • Pete Mack
    replied
    Here's the answer: the reason that V's Makfile.xxx OS-dependent and Compiler dependent files are stable is that they don't include any variant-dependent information.

    I presume you don't want to use autoconf and that sort of thing--it's a bad idea unless you know how it works. (The only downside(?) of this is that FA can't be included in any Linux distributions.) In that case you will want the following files:

    * Makefile.xxx for all non-generic-*NIX platforms (that includes OSX.)
    * Makefile.std for generic *NIX
    * Makefile.src, and rename it Makefile.inc. (You can't use V's makefile.inc unless you use autoconf.)
    * The current main-crb.c and osx/ subdirectory, and any similar up-to-date main-xxx.c, if they are different from yours. V has now has environment-dependent subdirectories for gtk, win, nds(?), and osx. ('Rowan' and others made a lot of improvements to main-crb.c after I stopped working on it.)
    * up-to-date main-xxx.c as necessary.


    Then:
    1. Add rough-and-ready .h-file dependencies to Makefile.inc (copy them from your most up-to-date Makefile.xxx)
    2. Fix the source-file list in Makefile.src
    3. Set the COPYRIGHT and VERSION variables in Makefile.inc (These are used by the various Makefile.xxx files for #defines and string-replacement--no need to change individual Makefile.xxx or any other files.)

    Then:
    Compile

    Then:
    Debug

    Leave a comment:

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