Lyon

[bitbot]

This version will look better at 16x16.

[Smilymzx]

Something in the rendering needs a little adjustment because of the streching effects enabled by default

Otherwise it is fine.

[Saxxon]

Something in the rendering needs a little adjustment because of the streching effects enabled by default

Otherwise it is fine.

If it's the strange pixelation with DirectDraw rendering then that's just the way DirectDraw works. I am working on true hardware accelerated interpolated rendering. You can turn off DirectDraw and save settings in the meantime to get software interpolation.

[bitbot]

Something in the rendering needs a little adjustment because of the streching effects enabled by default

Otherwise it is fine.

If it's the strange pixelation with DirectDraw rendering then that's just the way DirectDraw works. I am working on true hardware accelerated interpolated rendering. You can turn off DirectDraw and save settings in the meantime to get software interpolation.

The stretching looks fine.
Now that the inner window auto maximizes, shouldn't the main window default to 1x zoom? This should take car of those black bars...

[Saxxon]

The black bars are necessary because not everyone has the same aspect ratio. For example, my home monitor is a 5:4,
my laptop is a 16:10, and my work computer is a 4:3. The bars are in different places maximized on each of these setups.

Edit: Come to think of it, I could always add the option of turning off proportions.

[bitbot]

Edit: Come to think of it, I could always add the option of turning off proportions.

This would be cool as an option.

The black bars are necessary because not everyone has the same aspect ratio. For example, my home monitor is a 5:4,
my laptop is a 16:10, and my work computer is a 4:3. The bars are in different places maximized on each of these setups.

Black bars are fine when you maximize, but by default the main window should be at ZZT's resolution.

the program window could default to ZZT's aspect (640x350/640x400)

[Saxxon]

I've been lazy.

Updates to come sometime this week.

[bitbot]

#put pusher caused a crash.

Code: Select all

runtime error 202 

System.StackOverflowException
   at Lyon.Roton.Environment.Push(Int32 X, Int32 Y, Vector V)
   at Lyon.Roton.Environment.ActPusher(Int32 Index)
   at Lyon.Roton.Environment.Act(Int32 Index)
   at Lyon.Roton.Environment.ExecuteMain()
   at Lyon.Roton.Environment.ExecuteInit()
   at Lyon.Roton.Environment.Execute()

[Saxxon]

That is a forced crash due to a (0,0) vector in Push. I'll take a look and see what's causing it.

Edit: The forced crash was unconditionally crashing on a (0,0) vector. However, it should only crash with a (0,0) vector when the tile itself is pushable. I've fixed this.

[bitbot]

You eat bugs for breakfast. :)

[Saxxon]

You eat bugs for breakfast. :)

:D

The bugs you guys are giving me are easy. Most of them stem from a slight misinterpretation of the original assembly code.

The features above and beyond ZZT are the hard part ;)

[Saxxon]

Graphics interpolation is done on a driver-to-driver basis. Some graphics drivers will interpolate it automatically, some drivers will not. This actually leads me to believe the only way to get this fully implemented is to implement some Direct3D stuff. Probably not going to happen anytime soon (since software interpolation blitted through DirectDraw is just as slow at least using GDI builtin stuff).

Experimenting with a few more things. I may have the next build ready tomorrow.

[Saxxon]

The update did not happen as planned :) Sorry guys. Got a little behind in real life.

I can't seem to get a decent hardware-based interpolation with DirectDraw, so I'm going to limit the use of interpolation to software rendering only. I was also working on an aspect-fixed fullscreen mode, but so far I've run into issues with the primary surface and screen updates in the background (for example if a background app redraws its window, etc)

All the changes are in Lyon, except for the bugfix for pushers- that's the only fix in Roton this time around. Playability has not changed much (not that there's much else to fix there)

[bitbot]

That's alright, It'll be worth the wait.

Found a couple minor bugs: When a room has a time limit, you get hit automatically upon entering. (Happens when entering from another room.)
There seems to be a problem with "Re-enter when Zapped" the Re-enter X,Y coordinate is off by +1,+1 (See example)

TIMETEST.ZIP

(487 Bytes) Downloaded 204 times

Also, please include the final draft of the Lyon icon I posted above. :)

[Saxxon]

Downloaded the icon. I will investigate the Enterx/Entery and time limit bugs. They probably stem from the direct translation of code- ZZT internally uses base 1 coordinates (on CERTAIN things), while Roton internally uses base 0. The conversion is made during load/save.

Edit: Ha, the restart-on-zap bug was as a result of a hack I put in earlier. No longer needed now that the rest of the involved code works just like ZZT. I have replaced it with the proper ZZT equivalent.

Edit 2: I fixed the time bug as well. As a side effect of the code change, the timer will be closer to actual seconds (it was too slow before).

Edit 3: Rewrote sound effects code so that it would be easier to modify sound effects, should there ever be a need to. This will also make it easy to disable certain sounds (water for example). I will do the same with alerts. No change to the UI for this, maybe in the future perhaps..

Edit 4: Added "disable alerts" and "disable annoying sounds". Right now, that second one disables the sound effect and message for water/lava. Alerts are one-time messages such as "can't shoot in this place" and the "fake wall - a secret passage", etc.. there is no way to reenable them except to reload the world as it just zeroes out the sound effect and message.