As an IT guy, no offense, but FFS just open a ticket. Don't email me, don't call me, don't send me a message on Teams. Just open a ticket.
Seriously. If you expect companies to track issues on random web forums.... well, you'r expecting incorrectly.
That’s not to say they can’t improve upon the experience; I can’t tell you how many companies have dogshit support sites (not saying this is Line 6).
The nice thing about the QC though is that you can send a bug report right from the unit.Hey, at least they have an official tool to report for issue and bugs tickets. Fractal, much as i love them, still insist on using their forums - and don't get me started with NDSP and Discord.
Ouh... It might depend on what you search? I tried and I see results and the option to create a ticket if none of the results are related to what you want to report.
As an IT guy, no offense, but FFS just open a ticket. Don't email me, don't call me, don't send me a message on Teams. Just open a ticket.
Yes that part of the process is annoying. Once you get your ticket submitted though they seem pretty fast at following up.I'd missed that the first time. That worked. Thanks!
I’m surprised it doesn’t also trigger an automated response telling you ‘Thanks for the bug report. Your concerns will be looked into soon…’The nice thing about the QC though is that you can send a bug report right from the unit.
"Yeah, but I thought that emailing you directly would get my problem solved much quicker and avoid all the hassle..."As an IT guy, no offense, but FFS just open a ticket. Don't email me, don't call me, don't send me a message on Teams. Just open a ticket.
Unless Frank Ritchotte is managing customer service. One time I just said his name three times in front of the bathroom mirror, and a replacement Helix and RMA number appeared.Seriously. If you expect companies to track issues on random web forums.... well, you're expecting incorrectly.
Yes, and if you email them, things tend to go well. But Discord, JFC, don't even get me started...The nice thing about the QC though is that you can send a bug report right from the unit.
Where I work, they just wander into your office and say, "Sorry for interrupting your lunch." Which they proceed to do anyway."Yeah, but I thought that emailing you directly would get my problem solved much quicker and avoid all the hassle..."
As if every other fecker doesn't think and do the same, and, as people who don't work on the support desk, we've literally nothing better to do...
To be honest, I don't remember whatever conversation you and I may have had. (The last several months have been stooopid, which is why we always ask users to open a ticket.) Regardless, Ben hit me up on Teams, I personally confirmed the bug yesterday, Scott fixed it last night, and it will be in this morning's dev software build—and in 1.3.For what it's worth, the poor support rep I was talking to about the desktop app save bug was so confused. He kept insisting it was supposed to dump you back into the USER folder when you saved a preset. I told him DI had confirmed that wasn't expected behavior when it happened on the unit, and I just wanted to ensure that they realized that, while the bug had been quashed on the unit, it remained in the app. He finally talked with DI directly, then said, "I am not sure where the confusion is. He already knows about the bug, as you said. So how can I help with this? He says it will be fixed in a future update."
For what it's worth, I hadn't gotten any confirmation from DI that he knew about the application bug (I think he was on a well-earned vacation), but I told the support rep I'd been told the best way to report a bug was to open a ticket, so I did.
To be honest, I don't remember whatever conversation you and I may have had. (The last several months have been stooopid, which is why we always ask users to open a ticket.) Regardless, Ben hit me up on Teams, I personally confirmed the bug yesterday, Scott fixed it last night, and it will be in this morning's dev software build—and in 1.3.