Issues, Workarounds & Localization

you also have no tracking id / no mails acknowledging you successfully sbmited, no way to edit a report to add any useful information log etc.....

already reported to CCP, in the mean time i don't submitt those anymore, the curent one is way to painfull to use, with no answer watshowever, so i feel like i do it for nothing, then i don't do it anymore

then just give us a way to do it...ffs, just tell us where to find the logs the ingame tool is sending, and i'll shoot you a mail that will be 200% better than anything you "tool" currently allow us to send!

i do report bug daily as part of my job, for many years now, and sorry but i won't do it anymore using your tool.

it is by far the worst i ever encountered (and trust me some are really bad). it is just a painfull nightmare to use it actually, the older one, even if i can understand was hard for you guys to use, at least had the most basic features the current "new & better" one lacks.

tbh i can't even understand how one would ever consider a bug report without edition, and tracking, would be like creating a car with no propulsion nor steering wheel!

yup, and even the webpage works when it want, the last bug report i submitted using it, i might have posted it several time...maybe....because on submiting it resulted in error 500 5 time in a row, and no, nothing to do with my connection.

the fun thing is that a dxdiag would help, but you can't join it using ingame BR, and a previously generated BR cannot be edited, so you have either ingame log + BR, OR BR + dxdiag, but not all, this is also true for some window you cannot catch using ingame snaping tool, so you have to do it using webpage.....

tbh, the feeling this tool gives me is that CCP doesn't want us to bug report to avoid having tons of BR...... i would prevent ppl posting them, i would surely develop a tool like this one!

sadly, the BR tools is in the same state that many things in the game...half baked......meh this game used to be great.

i'm sure that rolling it back to 2010 would be better tbh, before the univ crap, when we still had exploration, when we wouldn't have an anemic server missing half the commands or taking ages to register them, and when game mechanics were reliable (and there are so much other things like the oh so great "launcher")

Have to agree with both CCP Devs posting here, just after Rubicon I posted a bug report (as requested by a different dev) regarding non-functional SLI in the DX11 version of the engine.

At roughly the same time I was doing checks on the drivers and raised a ticket with Nvidia directly and they advised that they weren't aware (or at least the team the builds the profiles) there was a DX11 version of the engine and confirmed that a profile would be added in the next WHQL drivers (now available).

Under the old system I could have updated the bug report so that CCP could stop any bug checks they were doing at least until the new drivers were out and contact Nvidia to see what (if any) additional information they needed on the updated engine. I was told that the solution was to raise another bug report. Surely we had this problem with the normal support ticketing system in the past?! Doing this to bug reports is certainly counter intuitive and under the old system the BH or other dev assigned the bug report could request additional information and tests from the reporting user allowing users to feel engaged in the solving of issues they have detected and reported.

I'm thinking we should bug report the fact that features have been removed from bug reports ... such as being able to update them ...

I try to submit bug reports but the lack of any player accessible tracking makes it feel like sending the carefully written report with precise reproduction steps with multiple screenshots demonstrating the visible effect of a bug that I know as a programmer is probably a simple one line fix into a black hole. For all I know the bug report isn't even being successfully entered into your tracker, the client freezing during submission isn't very reassuring.

I have to say that since I can no longer see the progress of bug reports, the number of bugs reports I submit has decreased a lot. Please prioritize this!!

It would much better if you had a good bug reporting system.

Oh and another hint, when you are doing something dumb...don't post on it. I mean the current bug reporting system it just horrible.

I've given up on bug reports it is so bad.

I didn't read the whole thread yet but I saw the dates of the posts publishing...

I will verify the current status of the Bug Report(s) procedure and try to comment on here.
{Or in bug report(s) if it applies, or both.}

I recently found a bug and was trying to find if there was a stickied thread and found none.

I then found the link to Bug Report is in the Support section of the website.


I then verified in the Support Tickets section if there was a related subject to the topic I was going to make a Bug Report about.
There is a section at the bottom related to it as well...


I see no way to save data related to the reporting process, neither in the Bug Report section or the Support Tickets section.
(I even found an email address from the Corporate site For Corporate enquiries and Business Development.
Under Contact at the bottom of the Support webpage, even though it wasn't it either.)

Usually, when I get those, I find ways to keep record of my communication or processes.
If I cannot do it electronically, or manually, I try to get a camera.
(Which often has to be controlled externally to avoid processing conflicts errors.)

It does get more complicated, the costs usually raise with the complexity.


Needless to say, it is a 1. totally different process to 2. have to pay someone else to 3. scan a document 4. to upload to an email address 5. to be able to attach in an email if 6. the data cannot be saved 7. on the terminal the data processing for the report occurs than say, 8. click a button to submit a report with data included inside.

It may take a few more years to be able to do that kind of work.

(by the way, did anyone notice the previous sentence is way too long..?)

And I even forgot to mention the dreaded forum post bug which wipes out the post content unless you copy paste edit in another editor to avoid working for nothing.

lol

Bump. This needed to be fixed a long ******* time ago. Any progress?