Borg for 320 is running.

[takkaria]

Originally Posted by Magnate

Could you be a bit more specific? Did you mean buggy loops (like I forgot the null terminator in slay_table so d_m had to rewrite all the loops in slays.c) or loops which work but cause problems? Can you describe them, either here or at trac.rephial.org? I'm happy to try and fix them.

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...

[Magnate]

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 ;-)

[Nolendil]

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

[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

[APWhite]

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.

[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.

[APWhite]

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.

[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.

---------------------------
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
---------------------------

[Nolendil]

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.

[APWhite]

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.