Gaming the “off-by-one” bug (difficulty re-target based on 2015 instead of 2016 block time span)?


Currently in Unity, if you have a spritesheet -- lets say a 6x6 grid of 16x16 tiles, and split them, and set the pixels per unit to 16 (thus making 1 unit = 1 tile). Then drag one of the resulting tiles to the editor, it looks fine. But if you start moving the camera around, it sometimes renders a column of pixels from the NEXT sprite. This because very obvious when you create a map of tiles -- about 25% of the tiles render with the wrong pixels on the edge (different ones display this issue depending on camera position).

This problem has been around for a while and there are some 'workarounds', but the whole purpose of using Unity, is to concentrate on game development, not fixing engine bugs.

So in summary: Fix the off-by-one bug so we can make "retro" pixel art style games in unity without...

0 0

I haven't logged into SourceForge for many years.

That said, just because you don't understand the change doesn't make it a "random numerical hack". It's very specific. You are off by 1. This adds "1.0" and corrects the texture offset. It does so without introducing any regressions that I can see, and I mentioned Dragon Quest only because your comment did, not because it was the only thing I looked at.

What I don't know is whether you are off by exactly 1.0, or if there is some rounding going on in the hardware that the code is instead truncating.

Your suggestion that the bug probably occurs later in the sequence is unlikely - if you mess with the texture coordinates any later than this line of code it affects all texture modes and DOES break other titles.

This line is pretty hairy - it's not impossible that an unexpected truncation is occurring. I suppose we could take this line apart and examine it more closely, but the assertion that this line is...

0 0

I have noticed when saving or loading that my games are not displaying properly.

Basically you get a picture of what you were looking at when you saved it and the name of the place you saved it at.

What is happening is that I have a file I saved while in sovngarde however the picture depicts me as in breezehome. Now the other issue is is that it will actually load me from breezehome and not sovngarde.

So what I am having to do is exit save area then go back in until it displays my saves properly after a couple attempts it will actually show the picture of me in sovngarde as well as the save file listing it as sovngarde.

Is anyone else having a similar issue or know what is causing...

0 0
Comment 1 Matthias Versen [:Matti] 2013-01-26 10:10:39 PST A patch in 2 different areas of the code can complicate the review but thanks for the patch ! You should also request a review from someone or the patch could be overseen Comment 2 Brian Smith (:briansmith, :bsmith, use NEEDINFO?) 2013-03-01 14:56:29 PST Comment on attachment 706768 [details] [diff] [review] firefox.diff Review of attachment 706768 [details] [diff] [review]: ----------------------------------------------------------------- We will have to check the security/coreconf fix into NSS separately from the toolkit/ fix. ::: security/coreconf/nsinstall/pathsub.c @@ +240,4 @@ > if (rv < 0) { > perror(myPath); > } else if (S_ISLNK(sb.st_mode)) { > + rv = readlink(myPath, buf, sizeof buf-1); Please put spaces around "-", i.e. "sizeof buf - 1" ::: toolkit/crashreporter/google-breakpad/src/client/solaris/handler/ @@ +511,4 @@ > ...
0 0
[Qemu-devel] [PATCH] Fix off-by-one bug limiting VNC passwords to 7 char [Top][All Lists] [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [PATCH] Fix off-by-one bug limiting VNC passwords to 7 char

Fix off-by-one bug limiting VNC passwords to 7 characters instead of 8 monitor_readline expects buf_size to include the terminating \0, but do_change_vnc in monitor.c calls it as though it doesn't. The other site where monitor_readline reads a password (in vl.c) passes the buffer length correctly. Signed-off-by: Chris Webb --- monitor.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/monitor.c b/monitor.c index 22360fc..6ae5729 100644 --- a/monitor.c +++ b/monitor.c @@ -433,7 +433,7 @@ static void do_change_vnc(const char *target) if (strcmp(target, "passwd") == 0 || strcmp(target, "password") == 0) { char password[9]; - monitor_readline("Password: ", 1, password, sizeof(password)-1); + ...
0 0
Official v6.30 Bugs thread

Official v6.30 Bugs thread


Steve Walmsley:

--- Quote from: alex_brunius on November 03, 2013, 04:14:21 AM ---Am I the only one that is still getting errors with missile bases for conventional starts? (Life support failures and errors making it impossible to advance time until they are deleted).

--- End quote ---

Is this for v6.30, not v6.20?


Yes, missile bases for conventional start are still bugged. I did a clean re-install and no go.

Also, when a TG is unable to perform its default order, the game displays a null error in addition to the normal log message. The error does not disappear after you remove the default order from the TG until a construction cycle has passed, at which point it vanished.

Fuel consumption for missile engines seem to be off by one decimal in engine size.

In version 6.20: 1.0 MSP = x3.00 Fuel...

0 0


I'm using the edge version of jQuery and jQuery UI provided through At time of writing, that's jQuery 1.10.2 and jQuery UI 1.9.2

I am on the Beta channel of Google Chrome, 33.0.1750.46 beta-m, but another StackOverflow user is able to reproduce the issue on the latest version of Google Chrome 32.0.1700.76

The operating system is Windows 7.

Here's a codepen to reproduce the issue: Here's a screencast of the issue reproducing itself:

Here's a stackoverflow post with confirmation from a second user and an OK workaround:

I am seeing the placeholder for a sortable appear at index + 1 when it should be appearing at index. This only occurs the first time the dragged element enters the droppable area. If...

0 0

PLL tones not programmed correctly. I used CHIRP to configure my new Alinco DR-135T. Set the PL tones to 162.2 as normal for repeaters around here. Upon programming the radio, they show up in the radio as 167.9. In order to get them to show up in the radio correctly, I have to select 159.8 in CHIRP. BTW, this does not seem to be a simple "off by one" error as PL tone 100hz correctly transfers to the radio as 167.9. In order to get them to show up in the radio correctly, I have to select 159.8 in CHIRP. BTW, this does not seem to be a simple "off by one" error as PL tone 100hz correctly transfers to the radio.

Configuration: OS: Ubuntu 10.04, CHIRP Version 0.2.3, Radio: Alinco DR-135T Reproducibility: 100%

I emailed this description to Dan Smith who added the following:
"It is an off-by-one, because Alinco doesn't include a few of the higher tones, making the off-by-one start somewhere in the list."

I stand by willing to assist in resolving this issue:...

0 0