Forgotten Hope Public Forum

Forgotten Hope 2 => Singleplayer and Coop => Topic started by: Michael Z Freeman on 06-03-2011, 23:03:04

Title: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 06-03-2011, 23:03:04
Here ! - http://code.google.com/p/forgotten-hope-singleplayer/

For my beloved Forgotten Hope single player experience  ;D

After some discussion with djinn and Remick04 I have finalised the initial set up of a Google Code issue tracker for Forgotten Hope single player and AI.

Please note that this bug/issue tracker is not endorsed by the FH dev team, but I did clear it with Remick04. In some ways it is just a more elaborate version of the "The Single Player Fan Project: Work to be done and feedback (http://fhpubforum.warumdarum.de/index.php?topic=10628.0)" thread. It can be used to track many of the issues with the AI reported on this forum to allow more efficient production of fixes. As always some of the fixes end up in the final build, some don't, nothing is guaranteed.

Anyone who is logged in with a Google account can submit an issue. The only set up issues I have is that I can't seem to allow users to add labels. I have labels set up for various common AI problem types and labels for each official map 16/32/64, or independent map. But only project owners and committers can add labels. The project admin has to manually authorise the addresses of people who want to edit issue metadata. I guess its not much of a problem as long as there are enough willing to become project owners and committers  and edit new issue submissions (triage) and deal with duplicate issues.

EDIT 06/07/12: Now the tracker is officially the preferred way to report SP/AI bugs ... see How To Report Singleplayer and AI Bugs (http://fhpubforum.warumdarum.de/index.php?topic=16801.0) in the Bug Reporting forum section.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: cannonfodder on 08-03-2011, 09:03:47
Good show old chap... :)


Correct me if I'm wrong, but hasn't issue number 3 been fixed?... :-\
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Raziel on 08-03-2011, 09:03:46
Great initiative DJ! Good work!
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 09-03-2011, 11:03:27
Cheers  ;D

I just put some issues in there as examples. If you PM me your gmail address I can give you editing privileges and you can fix them ... (sounds of people running for cover).
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Void on 15-05-2011, 18:05:33
RE: issue 24 (Crusader incorrectly set as armoured car)

-Found error in the AI Template plugins for all Crusader variants; strength type was incorrect. Patch kit posted on the code page.



RE: issue 12 (Crusader AA and quad .50 dont fire at aircrafts)

- Found incorrect settings for allowedDeviation vs Deviation in weapon ai template for Crusader AA. I need the correct asset name for  "quad .50"; I can't find it. Patch kit available after I know the object name for the quad.
 

Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 15-05-2011, 18:05:30
Good stuff ! Issue labels have been altered appropriately. Good to see Google Code coming into usefulness like this  8).
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: djinn on 15-06-2011, 09:06:48
Added a number of new ones recently. However, i accidentally added the AEC Deacon issue a second time. I looked, but cannot find a way to delete it. Please help.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 18-06-2011, 22:06:45
Hello djinn, I'm back from mai holiday  ;D ... I deleted the issue ... delete is in the drop down list bottom right of page when you comment / make changes.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: djinn on 19-06-2011, 00:06:58
thanks.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Void on 06-02-2012, 00:02:37
Hi all,

Just wanted to make it known that this tracker is the preferred method for reporting singleplayer bugs you might find in FH2.

You can report them elsewhere in this forum but I may never notice. The tracker I am paying close attention to.

Furthermore, the tracker now accommodates submitting fixes for bugs reported. Any bugfix that is submitted is a candidate for inclusion in the official build, though anyone wishing to see their fix go official must properly document their changes.

For more information refer to the documentation and faq on the issue tracker. 
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 06-02-2012, 02:02:59
Thankou Void !  ;D

This should contribute to making the FH2 SP/Coop gameplay an even higher quality experience.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 06-02-2012, 17:02:27
To be honest, the tracker at its current state looks neglected. Most of the opened issues have "New" status, default type, priority etc. Personally, I'm still waiting for feedback on my wall of text in issue #51, be it "confirmed", "don't understand what are you talking about" or "won't fix, because..."
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Void on 06-02-2012, 18:02:21
I will look at it now Gavrant.

True the tracker has been a little neglected. It has been up for a good while, before it became the official preferred means of reporting bugs. We are working to change this, though it still may take a little time.

Please don't get discouraged. Looking over issue #51 now.

Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 07-02-2012, 12:02:03
I'm still waiting for feedback on my wall of text in issue #51, be it "confirmed", "don't understand what are you talking about" or "won't fix, because..."

I don't know what your're moaning about really as that was only put in on Jan 29th 2012, but as Void says, it will be looked at.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 07-02-2012, 16:02:26
I was moaning out of fear, that my issue will have the same fate as issues dated Jun 2011. Besides, it's not just a bug report, it has fixed files attached. I desperately want to know does the fix work for other players, so I can get lots of much deserved thank yous :)
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Void on 07-02-2012, 17:02:29
Quote
I was moaning out of fear, that my issue will have the same fate as issues dated Jun 2011

I fixed crusader incorrect strength type about a year ago as a community  contributor. It never got in. Try not to worry, as we are trying to change that trend.

As for waiting for the thanks and praises: you get thanks from me already; but don't hold your breath for a huge round of applause. A few people will thank you, maybe, and you will go on a list of contributors I maintain but that will probably be it.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 07-02-2012, 20:02:52
That part about "thank yous" was an irony, though I must admit, with a grain of truth.

To switch discussion from me complaining, I have a question to you, Void, regarding the tracker: should we report bots getting stuck in statics? Or are you going to redo navmeshes from scratch anyway, so you don't need that kind of info?
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Void on 07-02-2012, 22:02:01
Quote from: gavrant
...Or are you going to redo navmeshes from scratch anyway, so you don't need that kind of info?

Yea. Gotta make new meshes for many maps, so bug reports about pathing errors aren't really helpful.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: cannonfodder on 08-02-2012, 08:02:40
Thank you in advance for any bugs/glitches/whatever you happen to fix.

Thank you, thank you, thank you.



Happy now gav?

:)
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 08-02-2012, 09:02:27
 ;D Yup, pretty happy! But official award from the community would make me completely happy. Maybe "The hottest man of FH 2012" or something...
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: djinn on 08-02-2012, 13:02:48
Dont worry, Gavrant.

we may seem to reply dismissively,

but like the regular devs and BT,

DJBarney, myself and Void are very in tune with the situation and will do our best to repair it.
You should see the emails that go across between us and how many people on Battlefieldsingleplayer we disturb to get solutions to issues.

We only reply the way we do because we mostly have little time online to do so... But let not the note fool you.

We are on top of it. I can't give you a time line for when as it all depends on how early a fix is available or how high in the priority it is (i.e how much it breaks gameplay).

Do help if you can by posting such fixes as you did. And it will be all part of what we use to make SP better.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 08-02-2012, 13:02:57
Djinn, everything is ok. Void contacted me by PM 2 days ago. I think, he took that issue into his hands.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 22-02-2012, 16:02:56
OK, been doing some work on the issue tracker. I think I've got it fairly ship shape. I made a page that will come up when the "Issues" tab is clicked on (http://code.google.com/p/forgotten-hope-singleplayer/wiki/InterstitialIssuePage). This comes before the actual issue creation part. There is a list of all the maps there to allow creating an issue for whatever maps with special label set for it.

There's some interesting possibilities here like keeping a list of various AI experts on the wiki who can be contacted about certain issues. I have a few other ideas but I don't want the tracker to become all "my" thing. Also please note, I've tried to include functionality that will allow usage of the tracker for community mods and maps.

Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 25-02-2012, 13:02:34
OK, been doing some work on the issue tracker. I think I've got it fairly ship shape. I made a page that will come up when the "Issues" tab is clicked on (http://code.google.com/p/forgotten-hope-singleplayer/wiki/InterstitialIssuePage). This comes before the actual issue creation part. There is a list of all the maps there to allow creating an issue for whatever maps with special label set for it.

That's nice, but I still think that allowing non-members to edit labels would be a better solution, at least for multiple-map issues like #69, #35 or #26. Yes, I know that it's not possible right now, but I found an issue on Google Code Support: Allow non-project members to specify labels when creating a new issue (http://code.google.com/p/support/issues/detail?id=9269). A person from Google said that if this issue gets 100 stars, he/she will "set aside some of the other work to investigate this". It has 81 stars at this moment, so, please, "star" it.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 25-02-2012, 13:02:20
I starred it  ;D
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 28-02-2012, 02:02:29
 :o Wow! How did it manage to get 20 stars in 24 hours? Sudden invasion of some project's tribesmen?
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 28-02-2012, 12:02:18
Yeah, noticed that. So Google are working on it now.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 09-03-2012, 18:03:44
DJ Barney, a question about Google Code internal mechanics: do project owners automatically get e-mail notifications about new issues or updates to existing ones? Or does it require some action on their part, like starring issue or being its owner?

And if I correctly understand the cake in your profile, Happy Birthday!
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 09-03-2012, 22:03:20
Yes, it's starring. Anyone logged into Google can star an issue and get notifications about it. You can star the project as well and there are various syndication feeds.

If you are interested in particular issue types or maps then I can add you as an email address to inform if particular labels are set.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 11-03-2012, 22:03:26
I guess my question was not clear enough. I thought that if someone is an owner of some project, he/she is 'auto-starred' to every issue of that project. Now, after reading Google Code docs, I see that if I want one of the owners to know about changes and if I'm not certain that he has starred the issue in question, I have to either send him e-mail/PM or hope that he is included in 'Administer -> Issue Tracking -> Activity Notifications -> All issue changes' mailing list.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 13-03-2012, 17:03:38
Sorry for the misunderstanding. Probably because I have so much new knowledge about the AI swimming around my head just by learning from interrelated issues and digging around in the FH files :D

To answer your question. Yes, owners (the one who originally submitted the issue) DO automatically get replies. See "Issue Tracker" section on this page - https://code.google.com/hosting/settings - for the settings associated with that:

Quote
Whenever an issue is changed by another user, send me an email:
(tickbox) If I am in the issue's owner or CC fields.
(tickbox) If I starred the issue.

There is the "All issue changes" that you point out but, as you can see above, there is also a "CC" field available for each issue (Carbon Copy). If you like I can add you as a project "Committer" so you can use that field and set labels.

Quote
Project owners may make any change to this project.

Project committers
may work in the project, but may not reconfigure it.

Project contributors start with the same permissions as non-members, but their role in the project is visible.

Hope that makes sense.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 23-03-2012, 13:03:47
OK, been doing some work on the issue tracker. I think I've got it fairly ship shape. I made a page that will come up when the "Issues" tab is clicked on (http://code.google.com/p/forgotten-hope-singleplayer/wiki/InterstitialIssuePage). This comes before the actual issue creation part. There is a list of all the maps there to allow creating an issue for whatever maps with special label set for it.

That's nice, but I still think that allowing non-members to edit labels would be a better solution, at least for multiple-map issues like #69, #35 or #26. Yes, I know that it's not possible right now, but I found an issue on Google Code Support: Allow non-project members to specify labels when creating a new issue (http://code.google.com/p/support/issues/detail?id=9269). A person from Google said that if this issue gets 100 stars, he/she will "set aside some of the other work to investigate this". It has 81 stars at this moment, so, please, "star" it.

Google implemented this, so I turned it on. Non project members can now set labels when they first submit an issue.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 23-03-2012, 15:03:31
DJ Barney, thanks. Just in time, I have a nice issue to report, will create it tomorrow.

BTW, have you tried issue backuper attached to issue #63?

Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 23-03-2012, 17:03:56
It's on my to do list.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: ksl94 on 29-01-2013, 19:01:56
I just had a CTD on Vossenack, which surprises me for it used to be very stable in the past. My server simply closed down without an error message.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 31-01-2013, 19:01:26
Ksl, by "in the past" do you mean "before Patch B"? And IIRC, you have made some modifications in game files. Maybe, those modifications caused the CTD?
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: ksl94 on 01-02-2013, 16:02:07
Unfortunately I can't remenber exactly when it went broke. The only modification that might have lead to the CTD could be that I replaced the current GPO of the mapwith the previous one in order to make the map playable again  :P .
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 07-08-2013, 19:08:47
I should say I've had a lot going on here and have not been able to work on anything to do with the tracker. This situation will continue for at least the next 6 months due to circumstances out of my control. So I'll still be around sometimes but if anyone wants to take up the slack then please step up  :)
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: gavrant on 07-08-2013, 20:08:11
Well, a large part of the issues on the tracker are already fixed in the SP patches (but I would not close them yet until they are published with an official release). A couple of the tickets are not SP related, like the commorose one. I will look into few other tickets. As for the rest, I doubt that it's possible to implement them with BF2 AI, only if through major perversions.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: jrivett on 23-12-2013, 14:12:39
I recently added a few new issues to the tracker for server crash issues on Brest, Mareth and Mount Olympus in Coop Patch C. Is anyone actively looking at the tracker these days? Is there something I can do to help? I'd be happy to review map files looking for issues but I need to know what to look for.
Title: Re: Introducing a SP community issue tracker (Google Code)
Post by: Michael Z Freeman on 13-03-2015, 16:03:27
Google is shutting down its Google Code service ...
Quote
Hello,

Earlier today, Google announced we will be turning down Google Code Project Hosting. The service started in 2006 with the goal of providing a scalable and reliable way of hosting open source projects. Since that time, millions of people have contributed to open source projects hosted on the site.

But a lot has changed since 2006. In the past nine years, many other options for hosting open source projects have popped up, along with vibrant communities of developers. It’s time to recognize that Google Code’s mission to provide open source projects a home has been accomplished by others, such as GitHub and Bitbucket.

We will be shutting down Google Code over the coming months. Starting today, the site will no longer accept new projects, but will remain functionally unchanged until August 2015. After that, project data will be read-only. Early next year, the site will shut down, but project data will be available for download in an archive format.

As the owner of the following projects, you have several options for migrating your data.

    forgotten-hope-singleplayer

The simplest option would be to use the Google Code Exporter, a new tool that will allow you to export your projects directly to GitHub. Alternatively, we have documentation on how to migrate to other services — GitHub, Bitbucket, and SourceForge — manually.

For more information, please see the Google Open Source blog or contact google-code-shutdown@google.com.

-The Google Code team

I don't think anyone has been using it. I'll attempt to do some final back up anyway.