Borg for 320 is running.

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • APWhite
    replied
    Originally posted by Nolendil
    I believe that my borg tends to do "short trips" although he's clevel 35 but I'm not sure I understood what "short trips" are.

    After reading this post and particularly that part...

    ... I immediatly updated and expected a change but still noticed the previous behaviour. Since I had only updated the binary, I thought a change in the Borg.txt file might be also needed but I didn't notice any change there.

    Is it still normal for a clevel 35 borg that went as far as dlevel 30 to do trips to dlevel 1-5 under some circumstances?
    If not, what would be the most appropriate time to get a savefile to determine if something is wrong?
    Is he giving you the 'short trips' reason for returning to town? Look for something like "# Returning to Town (short trips)" or some other reason for returning.

    Leave a comment:


  • Nolendil
    replied
    I believe that my borg tends to do "short trips" although he's clevel 35 but I'm not sure I understood what "short trips" are.

    After reading this post and particularly that part...
    At about clevels 20-25, when his maximum depth was about 9, he would stay too shallow in the dungeon. He would get to depth 5 but then want to return to town for his “short trips.” He will now stop the “short trips” at clevel 15.
    ... I immediatly updated and expected a change but still noticed the previous behaviour. Since I had only updated the binary, I thought a change in the Borg.txt file might be also needed but I didn't notice any change there.

    Is it still normal for a clevel 35 borg that went as far as dlevel 30 to do trips to dlevel 1-5 under some circumstances?
    If not, what would be the most appropriate time to get a savefile to determine if something is wrong?

    Leave a comment:


  • APWhite
    replied
    Originally posted by Netbrian
    Could you take a look at this savegame? The borg seems to have run out of fuel for its light source, and it starts going a bit crazy. Sometimes it will crash the borg (but not Angband) altogether.
    Wow, that was one freaked out borg. He must have watched the Lakers game and it fried his brain.

    It's fixed now. http://www.innovapain.com/borg

    Leave a comment:


  • Netbrian
    replied
    Could you take a look at this savegame? The borg seems to have run out of fuel for its light source, and it starts going a bit crazy. Sometimes it will crash the borg (but not Angband) altogether.
    Attached Files

    Leave a comment:


  • Netbrian
    replied
    Originally posted by APWhite
    Yes. It is related to how the screensaver is trying to calculate panels. The big screen issues have been known for a while but I can't seem to nail down the solution. Each attempt seems to create a memory overrun. When I fixed the message parsing and reading, then something else gets whacked. Until it is fixed, it is better not to run the screensaver with the big screen mode.
    Thanks for the information!

    Another question -- what's with the Borg's tendency to buy or sell projectiles one by one? I don't think it always did things like this.

    I'm also seeing oddities where the borg will show the message "need to refuel but can't!", and will constantly enter and exit shops. I'd attach a savegame, but it won't let me interrupt it for some reason.

    Leave a comment:


  • takkaria
    replied
    Originally posted by APWhite
    Yes. It is related to how the screensaver is trying to calculate panels. The big screen issues have been known for a while but I can't seem to nail down the solution. Each attempt seems to create a memory overrun. When I fixed the message parsing and reading, then something else gets whacked. Until it is fixed, it is better not to run the screensaver with the big screen mode.
    Do you consider it completely heretic to use game interfaces that expose exactly the same information that the map routines use to draw on the screen instead of screenreading? Because that's probably a pretty good solution.

    Leave a comment:


  • APWhite
    replied
    Originally posted by Netbrian
    Thanks for working on this!

    When I make the play window too big, I get the following message -- do you know why? I'm running this on Windows 7.

    Expression: y < DUNGEON_HGT
    ---------------------------
    Yes. It is related to how the screensaver is trying to calculate panels. The big screen issues have been known for a while but I can't seem to nail down the solution. Each attempt seems to create a memory overrun. When I fixed the message parsing and reading, then something else gets whacked. Until it is fixed, it is better not to run the screensaver with the big screen mode.

    Leave a comment:


  • Nolendil
    replied
    Oh, that's right, I always forget to report this.
    I had the same issue as Netbrain on XP and Win7. This error has been around for a long time.
    I think I usually fix it by using a bigger font size so, apparently, the problem comes from the number of characters displayed, not directly from the window size.

    Leave a comment:


  • Netbrian
    replied
    Thanks for working on this!

    When I make the play window too big, I get the following message -- do you know why? I'm running this on Windows 7.

    ---------------------------
    Microsoft Visual C++ Runtime Library
    ---------------------------
    Assertion failed!

    Program: D:\Games\Roguelikes\angband-3.2.0\ANGBAND.EXE
    File: .\src\cave.c
    Line: 948

    Expression: y < DUNGEON_HGT

    For information on how your program can cause an assertion
    failure, see the Visual C++ documentation on asserts

    (Press Retry to debug the application - JIT must be enabled)
    ---------------------------
    Abort Retry Ignore
    ---------------------------

    Leave a comment:


  • APWhite
    replied
    Originally posted by Gorbad
    What I also saw, is that the Borg really doesn't like {!*} inscriptions, it's not inscriptions in general, things like {@m1@b1@G1} work fine, it's jut the negation inscriptions. No big deal to not use them, I just noticed it from a savefile with auto inscriptions.
    Interesting. The borg has been able to de-inscribe an "!" object. That has been in place for years.

    <checking>
    Ahhh, looks like the game is asking for a confirmation now. NP. Fixed.

    Leave a comment:


  • Gorbad
    replied
    What I also saw, is that the Borg really doesn't like {!*} inscriptions, it's not inscriptions in general, things like {@m1@b1@G1} work fine, it's jut the negation inscriptions. No big deal to not use them, I just noticed it from a savefile with auto inscriptions.

    Leave a comment:


  • APWhite
    replied
    Originally posted by jtwadsworth
    Borg seems to get stuck on my 3.2.0 compile in OS X when doing certain things such as:

    Trying to destroy an artifact {cursed}
    Trying to brand missiles
    Trying to enchant with a scroll

    It seems the keypresses are not correct; perhaps they changed in 3.2.0 with the quiver?

    jtw
    Each of these three were known and fixed with the update from april 15. If you are using source code from after that date and still having a problem. Let me know.

    Leave a comment:


  • jtwadsworth
    replied
    Borg getting stuck

    Borg seems to get stuck on my 3.2.0 compile in OS X when doing certain things such as:

    Trying to destroy an artifact {cursed}
    Trying to brand missiles
    Trying to enchant with a scroll

    It seems the keypresses are not correct; perhaps they changed in 3.2.0 with the quiver?

    jtw

    Leave a comment:


  • Nolendil
    replied
    Originally posted by APWhite
    When you encounter problems with the borg, you send the savefile and a brief description to me at andrew@innovapain.com.
    Oops, I didn't make a copy of the savefile and it's now lost.
    I'll try and remember that for next time. Thanks for the heads up.

    Originally posted by APWhite
    EDIT:
    This is now fixed. Tested and seems to be ok.
    Great, thanks for the quick fix, awesome

    Leave a comment:


  • Magnate
    replied
    Originally posted by takkaria
    I think APW means loops in the borg, not in our code. The glare is because lots of game internals have changed, I'm guessing...
    [fx: innocent grin]

    But that's all for the better ;-)

    Leave a comment:

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