Hollywood forums

Heh,

Just realized DisplayBrushPart() can do scaling with standard tags. Wall slice texturing got quite a speed boost! It's a little less accurate looking though!

I will post the code in a couple of days for others to play with. Currently it's about 450 lines of text total. I will add comments, some more stuff and give you seven different raycasting functions to play with: 1. Filled walls, filled floor and ceiling. 2. Filled walls with distance shading, fille...

Just added some kind of a distance shading, so walls, floor and ceiling further away appear to be more darker. I think it's actually starting to look quite good!

Hi all, I thought it would be nice to start working on some 3D game stuff. Like always I'm 20 years behind the current stuff, so it's only a raycaster. Currently it's slow as hell with texturing on but I'm still working on it. Implemented are textured walls, floor and ceiling. Next I will try to add...

I dont think that is too heave stuff to do, especially now that you tell that you have Wolfenstein although the original 3D only working and slow. Raycasting stuff is simple compared to a real 3D environment. You need only basic math, like simple vector addition and basic trigonometry to handle rot...

Fortunately Hollywood is really easy to learn! Just study the examples, play with them and start doing some stuff of your own. By the way, I just ported some Wolfenstein 3D style raycasting stuff from C to Hollywood. It works but is very slow at the moment. I will try to add some lookup tables to th...

Is this a bug? Anchor point of a layer moves if you use it as a output device for drawing. Simple example: EnableLayers SetFillStyle(#FILLCOLOR) Box(#CENTER, #CENTER, 300, 200, #RED, {AnchorX = 0.5, AnchorY = 0.5, RoundLevel = 25, Hidden = False }) SelectLayer(1) SetFont(#SANS, 50) SetFontStyle(#ANT...

And im also wondering if i would be possible to send those buttons some sort of identification info. Like could you give while you crate button, despite using the same evttable something like button.name="unique name". That way you could do: switch msg.action case "OnMouseDown":...

For basically I am deleting the button inside which the waitevent happens before making those new buttons. So basically the buttons part and waitdevent and so on, could be kind of deleted too before they are done. But its stupid if it is so. Since im not jumping out of those that button until the n...

I think the reason simply is that you are calling WaitEvent() or CheckEvent() inside a buttons callback function. Try to move it to some other place.