Wolf4SDL Bugs?

With Chaos Software more or less being out of the picture (their website is back up, though, but I don't foresee any further development on Wolf4SDL), the gem that is Wolf4SDL needs to be maintained and continued - but also advanced. Frankly, Wolf4SDL needs to be taken in the same direction as ZDoom and subsequently GZDoom were taken in. It seems wasteful to do anything otherwise. But that is a long-term process and meant to be discussed at another time. As it stands the last build of Wolf4SDL is over a year old, so I plan on using that last release (1.7) to begin work on a continuation engine which will aim to be just that, a continuation with advancement in mind.

However, continuation must happen before advancement, and therefor I come to the purpose of this thread - Wolf4SDL bugs. I've been out of the scene for a little while and I haven't had the time to sit down and actually played any mods or even the original game(s) to hunt, detect and squish any bugs. Many of you, on the other hand, have! Therefor, for CanisSDL (it's the name I've chosen because I like the idea of calling major releases cute names like "Labrador" or "Beagle" or my personal favorite "Huskie"), I'd like the following for anyone and everyone with time on their hands that is willing to help with this little project:


Game Played: Wolf3d (Which publisher?)/Spear/Mod (Non-source modified mods only!)
Episode/Level: Which episode-level or level were you playing?
Situation: Describe to me, as accurately as humanly possible, the situation you were in? What sounds were playing, what guards where you facing, what weapon were you using and so on and so forth.

One of the first "advanced" features, while working on any bug reports, will be an actual bug reporting feature, I think. Something that users can post here or send to me that can aid in bug hunting with minimal effort on their part as far as describing the environment (because I understand that such things can be a bit....patience testing... at times). It is my intention to pump fresh blood into the veins of Wolf4SDL as CanisSDL, and I hope that it will provide a better experience for both modders and players alike.

CanisSDL huh? Are you continuing where you left off where I helped you beta test it before you disappeared (again)?

Not really, no.

Modding requires me to do a lot of other things besides code that I lack the time and talent to do effectively. I am good at coding, so that is what I will do. Judging from what is being done with ECWolf, it is making me want to code more than mod anyway, be it either a sense of competition or avoiding the snobbery of the DRDTeam forums I don't know - either way this is mostly just to satisfy my need for coding.

Well then good luck to you then

I'd kill for Ripper's todo and bug list, actually. For the time being I
will be working on having the engine being able to output useful
information for users and mod developers. If anything, no matter what
direction this is taken in (be it simple advancement or just cleaning
things up), information output is always a good thing. As far as I can
tell Wolf4SDL has no seriously useful information output or logging
system anyway, beyond your basic popup error system.

Some things I would like to get around to:

• Scripting system (Lua)
  
• Obviously ZIP-based modding support
  
• Modern resource formats
  
• Truecolor video mode
  
• Simple multi-player
  
• Expanding sound code to utilize a variety of sound and music formats (Migrating sound to FMod probably)
  

Some possible advanced features:

• Voxel static objects/pickups
  
• Configurable particle systems
  
• Advanced multi-player features like chat, teams, clans, deathmatch etc
  
• Expanding on plane-based effects, including cell-specific light levels, effects, tagging and so forth (will require a better map format)
  
• Human-readable map format
  

Hi Herman!

There's a running thread at DHW forum called Wolf4SDL released
under SDL Code Crackers which initially announced the project, people
posted what they thought, gave helpful feedback, and nowadays contains
the latest fixes for Ripper to apply to the Wolf4SDL source code. Anyone
compiling the EXE can (mostly) cut and paste these fixes into their own
source code and create their own "bug-free" vanilla EXE.

Here is the point in time of the last ChaosEdit release. All of the
subsequent fixes posted are NOT in the current version 1.7 of Wolf4SDL.

Andy

Chokster37 wrote:

Dr.Zin wrote:I'd kill for Ripper's todo and bug list, actually.

Here it is:

README.txt wrote:TODOs:
------

- Add PC speaker emulation
- Center non-ingame screens for resolutions being a multiple of 320x240
- Add support for any graphic resolution >= 320x200


Known bugs:
-----------

- None! ;D

"Canis" is an interesting name. Did it interest you because "canine" the next level up from a "wolf" (a more expanded / larger group)?

Pretty much, it needed to be a relevant title and something that doesn't require ridiculous amounts of explanations of esoteric knowledge. Most people understand the term of "Canis Lupus" and "Canis Familiaris". I suppose it does also hint to what I am trying to do, as well.

As for the fixes and patches, since I am more or less running off of bug free (such a weird thing to say), I will move right on in to doing some other things. Also, since I switched from Visual Studio to Code::Blocks, there is actually a nifty little todo list feature in it that picks up comments with "TODO" and sorts them in a dialogue for individual reading. So I can see some things which weren't in the ReadMe, so I will see about perhaps completing this Todo list of his as well.

Adding a little Latin into Wolf3d huh Zin?

Of course, Classical Languages still have their use .

Well that opens up a new door of Wolf3d mod titles to think of. I honestly can't think up of anything original.