Searching for beta-testers for WeiDU.

[the bigg]

JCompon was so kind as to provide me with moderative powers and a forum for doing beta-tests. Obviously, for the latter to be useful I need beta-testers 

So, I am looking for people interested in doing tests on each WeiDU release. If you'd like to help me out, reply in this thread (or PM, email, IM... me) to get access privileges.

Ideally, you should be able to guess where possible bugs hide, create ways to replicate them, and bug me until I actually fix them.
Skills with at least some type of weidu activity (writing .tp2 or .d files, the command-line interface...) are very also a requirement.
If possible, being able to compile yourself WeiDU and familiarity with diff could prove useful, in case there is a very quick way to fix a problem. (this is obviously needed if you have a Mac).
No OcaML knowledge is obviously needed, but will of course be appreciated 

Please reply numerous   

[Loriel]

As always, I'll help out on the Mac side of things...

[Avenger_teambg]

I hope you'll find the linux problem faster than i decide to learn how to compile weidu

[the bigg]

I hope you'll find the linux problem faster than i decide to learn how to compile weidu

The only linux machine I have access to is located at 200 kilometers (130 miles?) from my house, I access it via ssh over a 256/64 dsl line, and the wine version running is 2003-some-some.

Compiling weidu on linux is trivial (download&install ocaml, edit weidu makefile, make, make clean).
It's on windows that you need to fetch cygwin, make, ocaml, mingw... manually 

As always, I'll help out on the Mac side of things...

\me adds to list of people to forward to JC.
(note: if only you volounteer then there's no need to create the workroom).

[Hety]

I'm in.

Got skills in bug finding(unix administration is generally inding yer own bugs in cnig files).

Got skills in .tp2/.d writing(minor to none is some parts).

I can get familiar with diff if needed(i'm FBSD guy, we dont use diffs, we use ports ).

Also i can set up linux box for compilation if u'll give some tips on this matter.

Cheers.

[the bigg]

OK, thanks.

Please note that you need to be registered to access the forum.

PS: which platform are you on? Windows, *nix, or Wine?

[Hety]

Windows(XP SP2), FreeBSD. No wine coz it runs pretty crappy under fbsd(i managed to install it and windows xp on top of it, but it took like 12 hours and i dont wanna do it again tbh). I can install gentoo or any other linux distro for it if needed.

*i instaled vmware on fbsd. but nvm*

[the bigg]

Windows(XP SP2), FreeBSD. No wine coz it runs pretty crappy under fbsd(i managed to install it and windows xp on top of it, but it took like 12 hours and i dont wanna do it again tbh). I can install gentoo or any other linux distro for it if needed.

Well, no, I could (and should) install some kind of Linux (gentoo if possible) too, as next year I'll be studying Operating Systems at uni, and the end exam will feature writing a Linux device 

A Linux+Wine would be useful to try and debug Avenger's problems, though.

[Hety]

Uhh kay... average sys requirements for wine box?

[the bigg]

Linux programs do not have system requirements - they would just run slower. Linux can run quite easily on a 486 with 16 Mb of ram and 500 Mb of HD.

[Hety]

Bigg, i think

debug Avenger's problem

= play with GemRB? or i'm missing anything?

Requirements in that case = hardware on which mentioned software will run without any visible lag )=

[the bigg]

Nope, the problem is this: http://forums.pocketplane.net/index.php/topic,18470.0.html (and other related things).

[devSin]

numerous

In other words, I can, of course, compile WeiDU and check the features I most use, although I don't know if I have time to stress test things that I don't use (e.g., broken COUNT_2DA_ROWS wouldn't be a high priority for me). Up to you.

= play with GemRB? or i'm missing anything?

I thought of this lately. I thought you went to university for math, but now it's CS; any chance of you contributing to GemRB once you get further along?

[FredSRichardson]

Id certainly be happy to help with beta testing.  I was thinking I could try to verify that scripting (DLG/BCS) compiling and decompiling is working, and that the basic command line features are working.

By the way, is there any kind of regression test for WeiDU?  I remember Wes mentioning this idea a long time ago, but I don't know if anything came of it.

I'm wildly hacking the iwg2*.ml code, and I ran into some problems with that and the newer version of WeiDU (188 I think), but I suspect this comes down to something that shouldn't be too hard to fix (I guess folks eager to attempt to compile and run the old IWG2 mod should probably work with an older version of WeiDU anyway).

[the bigg]

I thought of this lately. I thought you went to university for math, but now it's CS; any chance of you contributing to GemRB once you get further along?

Yep, I switched this year (allow me to avoid details).

However, I've already enlisted in contributing to the engine of JC's Broken Hourglass by his offering (as it's being written in OcaML by Wes), so (*) 

@all (=loriel, hety, dev, FSR): thanks for your offerings; you should receive shortly the membership privileges needed to access the workroom.

Ave, please confirm if you'd like to join or not 

*: JC has gently asked me to make it clear that the only reason that might stop me from working on GemRB is time issues, not a non-competition agreement or whatever tentative of restricting my freedom of code.

[Avenger_teambg]

My problem with weidu is just partially connected to gemrb. The fact i use weidu with wine is that i haven't ported dltcep to linux, thus i use the original binary of weidu too.
I haven't tried to use a native linux weidu with dltcep, i'm not sure it works, but honestly I haven't tried it.

I use dltcep+weidu while programming gemrb mostly to write some test scripts or look at scripts quickly.

About joining the testers, yes, once i can use the newest version, i would report more bugs
But i'm not your traditional weidu user, i would probably find iwd2/pst script decompiler/compiler problems only.

[jadorelordinateur]

I can test with SoA and ToB but I need a little help for .tp2 and .d

[the bigg]

Could you tell me what parts of WeiDU are you proficient in, rather than those you aren't? Testing is for people who already know some tricks.

[the bigg]

Update - I have a bunch of bug-prone changes for 196 (I'm talking about backwards compatibility) and our lovely main tester is on holiday from IE. As such, anybody with the time and willingness to run a bunch of tests would be quite welcome.

Specifically, I need somebody to try to install as many mods as possible, to see if the tp2 or the .d cause any parse error (luckily, I don't have troubles with actually not working features, but just with a mod blatantly failing to parse, so no need to get your eyes bleeding by comparing and checking bits in a file).

As usual, you can contact me via post, via PM or via IM.

[CamDawg]

I can't offer any actual help at the moment, but I did want to say thanks.

[the bigg]

I can't offer any actual help at the moment, but I did want to say thanks.

Well, this is the last thing to do before 196 is ready. Not that I'm trying to blackmail you, of course 

[cmorgan]

OK, boss, I have asked you enough questions and made you suffer for long enough I had better turn around and help somehow

I have some knowledge (you can guess form my questions not much!), and no programming background or languages, but I do have the following:

• the ability and willingness to follow directions to the letter
• a set of BG2_SoA/ToB discs (US edition)
• a current fully patched, Baldurdashed, never-been modded BG2_ToB install
• a cable internet connection with bookmarked IE sites
• 2 to 4 hours now, and more tomorrow afternoon
• a burning desire to do something besides my own work

Please let me know how/if I can help in any way.

[the bigg]

Check your PMs.

[zefklop]

Nope, the problem is this: http://forums.pocketplane.net/index.php/topic,18470.0.html (and other related things).

I don't know if this is currently in your mind, but this problem wasn't there with weidu v125, but soon in v184 !

Sorry, I have not courage enough to check all version and see where the problem appeared !

[the bigg]

The problem surfaced when Weimer moved from using MSVC++ to gcc for compiling WeiDU. Moving back to MSVC++ didn't solve the problem. As far as I am concerned, a native WeiDU is much better than a wined one.