Kaiochao's site

Glitch or hidden half-feature?

Tue, 31 Jan 2012 01:41:32 +0000

If you set a map's icon-size to 0.01, it will stretch to fill the control without preserving the aspect ratio. That means, no more black bars!

The only glitch is that, when the control is resized, it requires a re-draw or else the map will be blacked out.

built-in 'bounds' variable

Mon, 30 Jan 2012 23:02:37 +0000

I just discovered this, because it shows up in the vars list. Why isn't it documented?

mob
    bounds = "16,16"
    Login()
        src << "[bound_width]x[bound_height]"
        bounds = "24,24"
        src << "[bound_width]x[bound_height]"
// Output:
//  16x16
//  24x24

I'm liking the variable aliases, like fps<-|->tick_lag, glide_size==pixel_step_size, etc., but they're only useful to me after I find out about them. Maybe the bounds variable is unstable or buggy or something, somehow. Or maybe you just forgot about it. I'm using it from now on, anyhow.

I would like, though, if vectors were supported natively. That is, like in Coggoid, properties that belong together should be the same variable.
For example, an equivalent of your x, y, and z would be pos = vec3(x, y, z). Colors would be vec4(r, g, b, a). Setting pos=1 would be the same as setting pos=vec3(1, 1, 1) since pos is defined as a vec3.
Vector calculations are definitely okay already (jt_vectors creates and garbage-collects new /vectors each operation), but a built-in alternative would be nice. Maybe I could make something using lists, but lists can't have chlidren.

Create /shading objects AFTER runtime

Sat, 28 Jan 2012 05:18:28 +0000

How about it? When you try to process on a turf that doesn't have a /shading object, create one for it on the spot instead of all at startup.

I didn't want to put this in the feature tracker yet because I hear things are buggy... Plus, I wasn't sure what this "applies to" when the options are for the BYOND suite and not relative to the library.

FILE_DIR look-up

Sat, 21 Jan 2012 16:55:53 +0000

I have a code file two directories in from the root.
".\blah\blarg\code.dm"

I have icon files referred to in the code file in a different folder in a different folder in the root.
".\bloo\blee\icon.dmi"

How do I set FILE_DIR in the code to reach the icons?

// This is how I would expect to be able to,
// but it doesn't work. (cannot find file error)

// code.dmi
#define FILE_DIR ".\bloo\blee"

obj/icon = 'icon.dmi'

// maybe this is necessary to keep the compiler cleaner?
#undef FILE_DIR

I figure doing this at the top of my code files would make it easier for the compiler. It doesn't have to look through every folder for every icon, just the folder I specify in the code file.

fat-peaked cosine graph

Thu, 19 Jan 2012 23:55:58 +0000

Excuse my badly drawn cosine graph.

Is it possible? If so, how?

Simplest Way?

Wed, 04 Jan 2012 22:55:37 +0000

I know Forum_account's Pixel Movement libraries handle it very nicely, but what I want to know is if there's a very basic algorithm for fractional pixel movement. What I mean by that is, of course, moving by fractions of a pixel at a time. The importance of that to me comes from usage of math slightly more complex than addition and subtraction (mainly trig).

The current basic "native pixel movement" requires you to shift positions by integer(s) at a time. This inaccuracy is problematic in a number of cases. Mainly, at higher frames-per-second, the minimum speed limit of 1p/t(pixel per tick) really noticeable. There are also obvious rounding issues with trig functions. They simply won't work with low speeds, causing you to only be able to move one of the 8 directions at rounded speeds. Using the "simple" Move(loc, dir, step_x + dx, step_y + dy) won't use BYOND's awesome pixel-perfect collision detection, where, if an object's bounding box intersects (or possibly even overshoots?) another, it is instantly pushed back.

What I ask for is the simplest fully-functional method that best uses BYOND's native pixel movement support while providing fractional displacements. Forum_account's technique is to build up the fractional parts and add the integer parts. Is there a simpler way that replaces less of BYOND's native functionality?

donate to BYOND!

Mon, 02 Jan 2012 07:27:16 +0000

BYOND (as well as myself) would appreciate it if anyone would extend my membership, preferably before the prices rise, but we'd be perfectly okay if you did afterwards.

Help BYOND! Help me!

Oasiscircle!
Thanks for the 1 year extension!

walk/step_to() pathing failure

Sun, 18 Dec 2011 09:59:42 +0000

Code:

step_to(A, B)

Problem description:
When src is trying to get from A to B with a big wall in the way (yes, walls are dense turfs, not dense objs)

  ||=====
  ||
A1||
  ||
A2||      B
  ||
A3||
  ||
  ||=====

step_to()/walk_to() will go to A2 and then get stuck (it returns 0). Is this a limitation of BYOND's usage of A*? Can it be fixed in a way that doesn't force me to use an A* library?

I did it

Tue, 22 Nov 2011 00:59:02 +0000

download (demo)

Now go do it better!

(because I have obvious rounding issues and I clearly have efficiency problems)

raycaster

Sun, 20 Nov 2011 23:24:41 +0000

download

Someone make me a pseudo-3D renderer with this (in DM).