|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336612]
|
Sun, 12 October 2014 15:50
|
|
hrvg |
|
Messages:158
Registered:August 2012 Location: France |
|
|
Hi silversurfer,
Thank you for your reply.
Quote:I downloaded the savegame but all mercs are in town, repairing, training, interrogating prisoners but no merc is in sector M8. :headscratch:
I am Idiot... :headbanger:
I sent the wrong savegame (AutoSaveJeu02.sav)
Good savegame is "SaveGame02.sav": https://mon-partage.fr/f/YPrOd1n4/
Sorry.
Quote:This should now be fixed in revision 7552.
It's not an automatic fix. You will have to pickup all affected items and move them to an empty slot to get their flags cleared.
Thank you for your explanations and patience.
Regards.
[Updated on: Sun, 12 October 2014 15:55] by Moderator Report message to a moderator
|
Staff Sergeant
|
|
|
|
|
|
|
|
|
|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336688]
|
Wed, 15 October 2014 01:19
|
|
Martyn |
Messages:1
Registered:October 2014 |
|
|
I'm running stable 7435 on Windows 7 Pro, under 1024 x 768. I'm running NCTH with new Interrupt system.
It's a great release, but I've noticed a couple of bugs that have already been fixed in later releases (is there a download page and change summary for those?), but also a couple of other things. These happen consistently with every game I start.
One is very minor: the log window blanks out when the sector inventory is opened, or when certain flyover text appears, or when a dialog box (e.g. wake/sleep alert) is closed. It only reappears when something that would refresh the log happens, like quicksave or scroll up of the log window. I could post a screenshot but it would just show a black log window like I describe. Otherwise graphics are perfect (aside from the 2-handed bug which I understand is fixed).
The other may or may not be a bug, but for me it makes 7435 almost unplayable. I am seeing this at the early part of the game -- I have not progressed beyond the middle sector of Drassen yet.
At all but point blank range, only head shots can be taken. An enemy standing in plain view gets a target cursor only for the head, not for the body or legs. It is almost impossible to target a prone enemy. Do you need a save game for this? If so I will be glad to provide.
This sounds a lot like the issue I've seen reported elsewhere, where mercs on roofs cannot be hit at all. It's like terrain interferes with line of fire excessively.
If this isn't a bug, is there a tweak somewhere that can adjust it?
Report message to a moderator
|
Civilian
|
|
|
|
|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336715]
|
Wed, 15 October 2014 23:52
|
|
Flugente |
|
Messages:3509
Registered:April 2009 Location: Germany |
|
|
SevenfmStrange bug in stable 7435 (release 7521 from SVN):
The game crashes at 08:34 with the message
Group27(AI) attempting illegal move from D2 to C1 (GROUNDBARRIER)
The bug was found in russian release, but is reproducable with english release, too.
Tested with clean stock 1.13, without mods.
Anyone can help with this?
save
Additional info from Buggler:
"Group 27 of ubGroupSize = 0 is created somewhere after compressing time with the savegame" Fixed (kinda) in r7575. What happened was that a group decided to mvoe from (2,4) to (1,3). So it could move west or north, and decided to move west first... which was a bad call, as that would bring it into the sea. Illegal move -> Assert and stuff.
I fixed that by having them check wether the first move is okay if there are two moves possible. This should fix this issue, provided there is any path in the first place...
However, this should not have happened in the first place! Unless I misunderstand the AI group waypoint system, they should travel from waypoint to waypoint horizontally or vertically, and never try both. Testing where that was set up is tedious though (debugging strategic AI in general is a pita).
Also, the group has size 0. I am not sure whether empty groups should be destroyed or need to be around for the Queen AI to find and reinforce them. :whoknows:
Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336901]
|
Tue, 21 October 2014 19:23
|
|
cptwinky |
Messages:4
Registered:September 2014 |
|
|
KeldorKatarnsilversurferWhat do you want to tell us by that? That you are too lazy to do any work but can complain nevertheless? Not exactly what this thread is for but way to go... :facepalm:
If you don't want players (who consider the game for a youtube let's play) to comment on the state of your work then you shouldn't be develping games. The only one making an ass out of himself is you. Publish work and you will get feedback for it, whether you want to or not.
This is the first stable release in years so sorry if I expected it to be actually STABLE. I've waited for this release before I considered making a Let's Play. Now I check the bug thread about it and it seems to be full of issues that tell me it's all but a stable release. So what am I supposed to say hm?
JA2 has never been known for its lack of bugs, even pre-1.13. I think the only way to see a truly bug-free and rock-solid version would be a total engine rewrite but that's a lot to ask of a handful of people working on this in their spare time.
Over the past month or so I've played an almost full campaign with 7435 (outside Meduna now) and it's crashed ~15 times total. It's always annoying when it happens, but it's something I've learned to live with as a JA2 fan. Save often and don't worry about it too much, just focus on the fun and guns.
Report message to a moderator
|
Civilian
|
|
|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336902]
|
Tue, 21 October 2014 19:31
|
|
KeldorKatarn |
|
Messages:37
Registered:May 2006 Location: Germany |
|
|
DepressivesBrotIf you expected a community project that people like to tinker with in their spare time to be absolutely 100% bug free and stable, then you have quite frankly lost touch with reality. Everyone appreciates constructive feedback including bug reports, nobody likes entitled slobs making snide comments about the perceived state of their work.
Intitled snobs eh. If you don't like players and expect everybody to shut up unless they help coding then maybe YOU have lost touch with reality. This is a game, people want to play it, if it has bugs, people will comment on it. Don't like that? Get the fuck out. Jesus. I've worked on tons of projects like these so don't give me that entitled snob bullshit. The only ones who've been incredibly entitled and agressive are you guys.
All I voiced was concern that this versionmight not yet be ready for a let's play and a comment that I expected would maybe have been a friendly "Yes there's still problems left we're already have plans for a first hotfix patch to fix the biggest issues remaining.
Instead I immediately got jumped on and insulted. Now look at those posts and tell me who's lost touch with reality.
But go ahead, treat people like that in this forum. maybe you'll reach a state finally where you have nothing but self entitled devs left who apparently think they're something better just because they can code and nobody plays your game anymore. Maybe then you'll be happy.
I was actually planning a big let's play promoting the game, your work and maybe also the Arulco Revistited MOD. All I wanted to check was how ready and stable the new version was for that. Instead of info or feedback on the state or comments like "we're working on it, expect a patch in 2 months" or something I get insulted and attacked for no reason just because you guys can't take any critisism from "entitled snobs" Well fine. Have it your way.
[Updated on: Tue, 21 October 2014 19:32] by Moderator Report message to a moderator
|
Private 1st Class
|
|
|
|
|
|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336907]
|
Tue, 21 October 2014 20:23
|
|
KeldorKatarn |
|
Messages:37
Registered:May 2006 Location: Germany |
|
|
TaisMain target of a stable release is not to introduce any new features and thereby bugs and even lower the amount of existing bugs with fixes.
The term stable is aimed at features, no new major features are added to this release.
then again, this is focused too much on developer needs- People who want to play the game don't care about what the state of the game is in some hidden code repository. They go to the website click on download and that's that. If theres a major release called Stable then they expect that released version ot be well checked and close to bug free. And that's a reasonable expectation if you ask me.
If I make a video about the game what am I supposed to say to my viewers: Hey there's a new version and it's a stable code base so nobody will add new features but hey there's still bugs that crash the game...
Yes I understand it's a ton of work, I worked for years on projects like these but if you release something on the main webpage after years finally then that needs to be a polished version. Why didn't you just make several release candidates first, marking them as such, getting them out to the public, get bug feedback, crush those remaining bugs and only then release a new stable version. OpenTTD does it like that and they run incredibly stable and nearly bug free. on every major release.
AS for my comment having no purpose, oh? I voiced concern about the number of bugs remaining and that's feedback of a concerned player who wonders whether the game is ready for a let's play yet, where tons of crashes and problems are just a no-go. If you think that's a useless post fine.
Report message to a moderator
|
Private 1st Class
|
|
|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336908]
|
Tue, 21 October 2014 20:25
|
|
grim |
|
Messages:344
Registered:July 2006 Location: France |
|
|
KeldorKatarnConsidering this is a major stable release there seem to be a lot of problems still...
No, not that much considering the improvements since last stable release.
It's just that several dedicated persons take time to post bug reports in this specific dedicated thread. If there was noone doing that and the bug reports were spread all over different threads, the stable version would appear less bugged to you, maybe.
Quote:Why didn't you just make several release candidates first, marking them as such, getting them out to the public, get bug feedback, crush those remaining bugs and only then release a new stable version.
There was some, but not exactly entitled "Release candidate". There were bug reports on it too, but not everything got fixed. It's a big game with a lot of features and each game is very long, unique. Plus there are only a few coders out there to fix the bugs and it's not the most fun thing to do, nor their unique goal. Please bear with the community's work.
[Updated on: Tue, 21 October 2014 20:33] by Moderator Report message to a moderator
|
Master Sergeant
|
|
|
|
|
Re: Bugs: 2014 Stable 1.13 Release (7435)[message #336911]
|
Tue, 21 October 2014 21:15
|
|
Flugente |
|
Messages:3509
Registered:April 2009 Location: Germany |
|
|
When we had no 'stable' release, people were complaining daily about the last 'stable' being so old, meh meh whine whine.
The only difference between stable and unstable is that the unstable release has the current trunk version. Stable is that minus all features that came after Jan 1st 2014. Bug fixes go to both branches. You can also replace 'stable' with 'outdated' if you want. JA2 has never been bug-free in the last 15 years
There is no dedicated bug-fixing team. If someone decides to fix a bug, he does so. Which is getting more and more complicated by the way, as people often just give a very broad description of the error, without naming the exe version or providing a savegame.
Nobody is contracted to code anything but what he wants. If it fits into the game, it goes into the trunk, otherwise not (one could argue that some stuff that is in doesn't, but nobody does that).
Also, you threaten to not do an LP? We are not a company. We do not get any money if more people play it. I don't give a damn on whether you do an LP or not, or if hundreds of people play the game or not.
Report message to a moderator
|
|
|
|
|
|
|
|
|