Yes, both personal and anecdotal, neither of which are worth the pixels they're printed on.
I found
this with a quick google, but its out of date and published by Atlassian whose tools are specifically built for Agile development and you would expect their survey to reflect that, but they still see a very high percentage of developers using Waterfall in the traditional gaming space and note that as surprising, with "non-traditional" gaming being where people are using more modern software development methodologies.
As to
why... there's probably a serious games journalism article to be written there.
e:
Its also super common for "Agile" to
not actually be agile, just Waterfall but with a burndown chart, where things like end of sprint reviews are skipped because they "take too long to do", milestones are set in stone regardless of actual team velocities and velocities are expected to adjust to reach the milestone rather than the other way round, and all sorts of other waterfall-but-not-really-waterfall fuckery