Pics the Devs need to look at
- Thread starter Hooplah
- Start date
Invisible rocks
Lilly pads
Lilly pads
Someone once said, "One look is s worth 1000 words". Lawyers love it. Thus we don't need a ticket to vote it up.
I'm thinking not to fix that poor NPC stuck in 'quicksand' but lots of pics where the Devs can look at them and see
the leaks in their programming between all those fancy polygons and the collision math that doesn't always work.
With enough pictures from the players it gives the Devs info for a GLOBAL fix. Much better.
So I'm thinking post weird anomalies where rocks are hovering above the ground, an SRV wheels or ship landing
gear are buried halfway into the ground or a ship lands but didn't touch the ground like it is hovering. It is a collision
programming issue.
Regards
Last edited:
Yeah, when did these lilly pads start appearing? I don't recall seeing them until after the last patch (#4).Lilly pads
It does seem to break the ED immersion with some weird computer graphics.
Last edited:
Well let it play out a few days and see how it works. I'm trying to help the Devs with a lot of info for the most complex game ever invented. We'll see...
Just joshing around. I'm right there with you. Feedback is important.
No, but you need a ticket none the less, to kickstart the whole process off, and to which people can add similar examples.
No you don't
I haven't raised a ticket in ages, there's usually already one (or more) in there. But if people post links to existing ones I'm happy to add to them. And if no existing ticket exists it's probably not a big deal.
Floating bodies
Barrel doesn't quite fit in the cupboard
No you don't
I haven't raised a ticket in ages, there's usually already one (or more) in there. But if people post links to existing ones I'm happy to add to them. And if no existing ticket exists it's probably not a big deal.
The link you gave was to a new tracker - which is akin to a ticketing system (same difference) - raise a report [ticket] and people can upvote it.
So, yes, you need "something" (report, ticket, whatever you want to call it) and people with similar experiences can pile in to lend support.
My point being, saying you don't need a ticket [report] is untrue. There has to be 1 for the devs to be aware of these issues. All the posters in this thread, if they knew which report was created for it, could easily post evidence here and upvote there ... <shrug>
The link you gave was to a new tracker - which is akin to a ticketing system (same difference) - raise a report [ticket] and people can upvote it.
So, yes, you need "something" (report, ticket, whatever you want to call it) and people with similar experiences can pile in to lend support.
You think the Devs never fix bugs unless there is a ticket?
I think I already covered the rest of your points in the post you quoted.
There you go. Great post.
In a "proper" organisation the correct answer is no - devs don't fix tickets without a bug report/ticket/something - it's all about change control.
As for FDEV, well, your guess is as good as mine.
I guess by "proper" you mean they would raise a ticket themselves then prioritise it? That's what I assume & why I haven't raised a ticket myself in ages, only added to ones that are already there.
Different people have different priorities, bugs don't really bother me all that much (but they can be funny
).This is starting to feel like pulling teeth mate.I guess by "proper" you mean they would raise a ticket themselves then prioritise it? That's what I assume & why I haven't raised a ticket myself in ages, only added to ones that are already there.
Different people have different priorities, bugs don't really bother me all that much (but they can be funny
"Proper" .. in the context of an organised, mature company, that uses controls to implement changes. They follow frame works, like ITIL (link), to ensure these changes do not disrupt the business. That is what a normal organisation does - track changes, kicked off by some process. By separating "proper" and FDEV I was being facetious. FDEV do appear to be following some process, which is why they issued that tracker so the end user can raise issues, for FDEV to start the change process. Whether a CM raises the ticket (by scouring the forums), or internally someone raises the ticket after playing the game
, or by us using the report link provided is moot.The comment by Hooplah of
flies against what FDEV specifically asked.
So, for the last time, raise a report/ticket (only takes 1 person), then everyone else with a supporting "funneh" can post here for a laugh, and if they are at all bothered by it (so not you) they can lend support by adding to the report online. With enough "votes" on that report FDEV will be more aware of it and hopefully fix faster.
/thread.
Last edited: