Message Boards

The bigger problem lies in the fact that no one on the dev team actually has or uses that product.  For some time we had active developers that used vc6, but even those are now slightly messed up.  Once the source becomes public and we find someone who's willing to maintain the project files, it's entirely possible we will offer them.

Yes, and to go with that, I should note that most program suites have import functions for loading project files from earlier version.  People should be able to do this, but if someone does so, they should consider uploading the resultant project file and becoming it's maintainer.

I would however appreciate in the future if you didn't simply tell me what I should do.  If you want to offer your own brand of advice, I won't stop you (unless it goes against the rules), but know that I'm not just going to do what you say because you tell me to.

EDIT: Also, live patch?  I'm not sure what you mean by that...

Oh, I don't expect you to take my feedback as raw advice, just listen to it.  I look at things from a much different angle.  It sometimes can be useful to get my perspective, as often you need to combine both for a complete solution.

BTW, you are taking my advice like a textbook, a test lan can be a couple of old computers, or even a few VMs on your main desktop. 

Be interpretive with advice. Stuborness is an inevitable human trait that every person here has including myself and we each also have our own viewpoint.  However, if each one of us uses 1% of the logic possible to be gained from reading each other person's viewpoint, we all would become far better at everything.

When I give what you call advice, it may be phrased as such, but it is more a proposed theory, than advice.  Maybe it's a little old-school to think that way, but sometime's it helps to compair theoretical notes.  Maybe I need to scale back a bit on the frequency of reporting such notes, and we can meet somewhere in the middle.

Quicker than any of us, that's why your in charge.

What are you talking about? I fail to see how the bug I posted has anything to do with Vista compatibility.

I'm saying another similar one could occure just from switching to Vista native binaries, because of the overdue modularization and "other changes" to the Microsoft libraries.     Things that were the previous monolithic dll libraries were changed into metapackage-libraries, which load a big list of dependent libraries.

I'd have to go with custom made for Multiplayer (more iWads = more potential = more fun) as of the SP, does one have to choose.  I guess anything other than the lame attempts by amatures to develop SP iWads.  Only a few Ammatures have ever made a good single player game that wasn't a racing, flight sim, solitare or puzzle game.

According to Microsoft, most developers that encounter programs should be able to simply recompile, however since when do you take Microsoft's word as fact.   Anyways, it's worth a shot, but you may run into a few more overzealous cheat kick bugs, so be forewarned.

Could an index of files be given, with headers only, for those of us interested in the development, and compatability with other cocurrent projects.  I'm in early planning stages of a progressive bleading edge port, that doesn't plan to take the fast route OdaMex is taking, but a much slower route that will result in a code base usable for backports of features to all major GPL Doom versions.

Also, if you could post some of the resources you have been given for your project it may help other projects coordinate.  Remember, you are on the leading edge of development, and nice diplomacy will really help.

BTW I truely do understand the source issue, despite it being frustrating.

I'm starting to join.  I still need to get all my contacts together.  I go by ThunderFox on most other forums, most of you should know me by that name.

The first thing I want to bring up is the question of a milestone plan.

What is the current milestone plan? If any?  Do you need someone to handle that, and code review?

Obviously the first key component will be to isolate and replace all non-GPL code from source projects, and select libraries.  I personally recomend arts for audio.  It's never given me trouble on any of the Linux apps I regularly use that utilize it.  It also is entirely platform independent.

The second option is to continue with the zDoom system, or to port key functions, such as scripting code, and level function support to another more GPL-friendly Doom engine, such as Doom Legacy.

A third option is the renderer.  Should we stick with the current one from zDoom, or put that as a 1.0 requirement as well.  I'd once again lean on SDLlib for that.  Obviously we need to make up our minds on everything before the first milestone.

The final point is at what point do we make source releases of milestones, and at what point do we make binary releases?  Also, how big a bug mandates a backpatches to one of these milestone branches, and what size can be said "just wait for the next milestone"

Regular code cleanups would help, and it seams nobody is assigned to this.  You'd be surprised how many bugs can be traced just coincidentally with just this work.

I'd gladly take on these two organization tasks, and be sure to deligate enough that people can work in my absence.

Now I'll head over to the buglist to find a list of bugs that I want to try my luck dirrectly on when I get a SVG logon.