-Philosopher- uploaded file Gamma 09 Won_t End.zip (110.4 KiB)

Berserk Cyborg changed status from new to closed

Berserk Cyborg changed resolution from `` to closed

Berserk Cyborg changed blocking which not transferred by tractive

Berserk Cyborg changed blockedby which not transferred by tractive

Berserk Cyborg changed _comment0 which not transferred by tractive

Berserk Cyborg commented

Yes, this is a very old bug with the final Gamma mission and will probably never be fixed until the mission scripts are converted away from the old WZScript API to JavaScript. See ticket #2126.

The campaign in 3.2.3 is indeed very bugged, however, if you really want to play the campaign in the 3.2 series, I suggested you help test the git master (development builds) found here: http://buildbot.wz2100.net/files/.

The campaign is under heavy bug fixing/testing and the two current testers have only just begun reporting on Beta. See topic http://forums.wz2100.net/viewtopic.php?f=1&t=12714. It is already much better than 3.2.3.

So you would need to start a new campaign on master builds to see if any of the bugs you found still apply.

Don't like to give bad news, but in regards to responding to bug reports, The Project team members are very busy and are already overwhelmed. There just are not enough people to help us at the moment. They work on Warzone2100 in their free time should they choose so and, as such, means that progress is a bit slow.

Again, if you find bugs with campaign scripts or want to engage in discussion about the campaign in general for the 3.2.x campaign, then please report in topic http://forums.wz2100.net/viewtopic.php?f=1&t=12714.

-Philosopher- commented

Actually, that's all good. I was mostly just looking for a pointer on how to proceed.

This is my favourite game so I'll help in any way I can. I never played the original but I've enjoyed the versions this effort has created for many years. Through all that time I never bit the bullet and jumped in to help but perhaps now's the time to start. Bear with me while I get up to speed.

It also seems that two years ago, I actually contributed to the discussion on #2126 too (!). Seems I've forgotten much. I knew there was some trick to getting it to complete, but couldn't find it again this time around. Er... thanks for directing me to it. I was wondering why I'd already created an account here. Is there a way of viewing your previous activity (posts, comments) here? I couldn't find it.

I'll join in testing the campaign and do what I can. Happy to start a new one and work through to where everyone else is up to.

I take it the latest is in http://buildbot.wz2100.net/files/master/... same thing in the top level right? warzone2100-master-20170911-070427-7515753.exe as of today? I take it I don't need to download the updated campaign.wz mod etc. anymore as the latest is in the git master?

The build master doesn't give options for different resolutions. Is it restricted to 1024x768 for a reason or can I change it to match my monitor (as I usually do)? I've changed it, but let you me know if you want it run at a consistent resolution for testing purposes (if so, I'll put it back).

I'll read through the campaign testing thread but if there are any other pointers you can give me for getting into this properly let me know.

I have some other (not-campaign-specific) bugbears. What's the best way to join the discussion on their future too?

• CB Radar behaviour. Unusable on a mobile unit in 3.2.x - they just rush towards the artillery piece (overriding retreat/repair orders) and suicide themselves on whatever defences are inevitably in front of it. 3.1.x (and before) they acted as a shot fall detector - both practical and realistic, IMO - why was it changed?

• How do you stop a unit from moving or doing certain things automatically? In 3.1.x and earlier you could turn all these off. In 3.2.3 combat units always chase things that come into detection range, and trucks automatically join and contribute to half-built objects nearby. Makes it very difficult to post sentries that don't leave their posts and keep trucks on stand by to repair specific structures. What was the rationale behind these changes and can such features be reinstated?

• Radar detector sensors - never did figure out how to make these work. I assume they're bugged (they never prioritise artillery onto sensors within range - that's the point of them, right?) but perhaps I don't have the knack/understand.

• Templates. Yes, including in the campaign (because I replay it periodically). Seem to be quite bugged in the latest version (units seem to be forgotten all the time) but never really worked properly. Can you point me to the discussion on this topic?

• Difficulty selecting units. If the (e.g.) research window (F2) is open, commands to select units don't work properly - includes both clicking on them and selecting them by group number. Also, is there a hot key for exiting/closing the research window, build window, design window etc.? The only thing that reliably works for me is clicking on an inactive area of the window and often not even that is reliable. Are there any current bugs open/reported on this and/or discussion?

Berserk Cyborg commented

Yep, master is all that is needed. Just for reference everyone is up near Beta 3 in terms of testing. The two active testers are playing on the new insane difficulty (it can be quite challenging) although you can choose whichever one you want.

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore so I will revert it shortly.

It is best to just create new topics since the forums will bring in more answers than mine. There is one rather heated topic about primary/secondary unit orders in http://forums.wz2100.net/viewtopic.php?f=6&t=12197. The last two bullets have tickets ("View Tickets" tab near the login area). The beta guide in http://betaguide.wz2100.net/ has keyboard hotkey information.

pastdue commented

Replying to Warzone2100/old-trac-import#4635 (comment:3):

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore so I will revert it shortly.

As a heads-up, I am readying a patch that robustly fixes this and also enables high-DPI support and display scaling. (Not a problem if you revert that change, because it isn't required with said upcoming patch.)

Forgon commented

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore

Be specific. Who are these people and where are their bug reports?

-Philosopher- commented

Replying to Warzone2100/old-trac-import#4635 (comment:3):

Yep, master is all that is needed. Just for reference everyone is up near Beta 3 in terms of testing. The two active testers are playing on the new insane difficulty (it can be quite challenging) although you can choose whichever one you want.

Copy that. I've started catching up ASAP. Working through Alpha 06 atm. Not much to report so far (i.e. good news) but I'll add a comment in the thread with my findings to date when I'm up to the same level as everyone else or I hit some sort of significant issue - whichever comes first.

I'm reading through the thread you directed me to so I have all the context too - no point posting old news ofc.

I'm just playing on Normal - i.e. default - difficulty, as I suspect that's where folk new to the game may start (and it sounds like insane level is covered off, although I may give that a go later too).

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore so I will revert it shortly.

Well, I guess I'm one of those people, but I've noted the upcoming patch pastdue mentioned. I'll look out for it. Not an issue in the mean time. I could change it in the settings file easily enough - just wasn't able to choose it via the options menu.

Just wanted to check there wasn't some specific reason it was limited to 1024 x 768.

It is best to just create new topics since the forums will bring in more answers than mine. There is one rather heated topic about primary/secondary unit orders in http://forums.wz2100.net/viewtopic.php?f=6&t=12197. The last two bullets have tickets ("View Tickets" tab near the login area). The beta guide in http://betaguide.wz2100.net/ has keyboard hotkey information.

Thanks for the pointers on all of these. I'll join in accordingly.

Forgon commented

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore so I will revert it shortly.

Well, I guess I'm one of those people, but I've noted the upcoming patch pastdue mentioned. I'll look out for it. Not an issue in the mean time. I could change it in the settings file easily enough - just wasn't able to choose it via the options menu.

I'm curious as to what exactly causes this problem. Which OS do you use?

-Philosopher- changed _comment0 which not transferred by tractive

-Philosopher- commented

Replying to Warzone2100/old-trac-import#4635 (comment:7):

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore so I will revert it shortly.

Well, I guess I'm one of those people, but I've noted the upcoming patch pastdue mentioned. I'll look out for it. Not an issue in the mean time. I could change it in the settings file easily enough - just wasn't able to choose it via the options menu.

I'm curious as to what exactly causes this problem. Which OS do you use?

Windows 10 (sadly?).

I changed the resolution manually as per http://developer.wz2100.net/wiki/NewFAQ#HowdoIchangemyscreenresolution, and was otherwise just going to wait for the aforementioned patch to land before looking into it more deeply, but let me know if you need detail before then (and let me know what you need).

That said, not sure how much help I can be. My config has been static for some time and the issue (not being able to change the resolution in the options menu) doesn't occur in previous versions (including 3.2.3) so I'm assuming it's something introduced in the latest build masters rather than something to do with my video hardware/software.

pastdue commented

Replying to Warzone2100/old-trac-import#4635 (comment:7):

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore so I will revert it shortly.

Well, I guess I'm one of those people, but I've noted the upcoming patch pastdue mentioned. I'll look out for it. Not an issue in the mean time. I could change it in the settings file easily enough - just wasn't able to choose it via the options menu.

I'm curious as to what exactly causes this problem.

I posted a brief overview of the issues with the patch in #4623.

-Philosopher- commented

Just read it. Not being familiar with the code I only really got the gist, but I think that's enough. Looking forward to the revised patch. Do you know if it'll be posted in the campaign testing thread when the patch lands? The question has come up with the other active testers e.g. http://forums.wz2100.net/viewtopic.php?f=1&t=12714&sid=41c09336d7bb71d418b686c478ec79dc&start=120#p137577

alfred007 commented

Replying to Warzone2100/old-trac-import#4635 (comment:5):

There was a patch that recently attempted to fix showing resolutions below what Warzone2100 supported (#4623). It worked for me when I tested it, but some people report they can't change resolution anymore

Be specific. Who are these people and where are their bug reports?

This bug is reported in the 3.2.3 testing thread in the forum like vexed allowed when he opened this thread. One of the testers is Bethrezen and he reported his logs at the link below.
http://forums.wz2100.net/viewtopic.php?f=1&t=12714&hilit=resolution&start=120