Definitely. Worked with Japanese companies (not gaming industry) a while and it's quite challenging.
The time difference with central Europe was a big issue. Due to almost no overlap in working time we communicated a lot via email but if there was misunderstanding we had to wait a whole day to try again.
Then the Japanese colleagues tended to be very positive but "yes" often didn't mean "I agree" or "I understand", more like "I acknowledge that you said something". To actually get their approval you had to explicitly check if they agreed and basically quiz them to find out if they understood what was said.
Also a big part of software development is to finding and avoiding bugs. However, they were not very open to it, especially if we called something a bug or potential flaw. That made them lose face to their superiors and they got super defensive and didn't want to improve anything. Instead we had to call all their stuff amazing and disguise bug reports as suggestions for improvement or feature requests.
In general their approach was quite difficult from ours. We had a few testers that did a lot of exploratory testing and actively tried to break things. We developers thought a lot about potential race conditions and stuff like that.
The Japanese guys had a ton of testers that focussed on the most common use cases.
When we reported e.g. a sequence diagram, logs and a description how to trigger a race condition or a different kind of bug (often requiring a specific timing or uncommon sequences), sometimes with catastrophic consequences, they filed it but didn't fix it with the (understandable) reason: Our testers performed this use case 10000 times and never triggered it. It's extremely unlikely to happen in production and we will fix it once a customer reports this problem.