He's working on a game and is having a common, but frustrating, issue with physics. We've workshopped it a bit and I think he's got some potential mitigations or improvements to try. It may be solved soon! Or it may persist and bug him for ages, we'll see.

Some more details:

• He works on this project part time

• He's a competent coder, but not terribly experienced in working with models and colliders yet

• The game in question is 3D, physics-based, and multiplayer (so everything must be synced within reasonable tolerances)

• It is a solvable problem. I think I've identified and shared something that may help, but I don't remember all the nuances perfectly

• He often sorts nagging issues out within a week or two if they aren't too involved

• We usually meet weekly, but I'll be sure to ask about the bug if we skip our next call for whatever reason

• Solving the issue at hand is sufficient, even if it opens a new can of worms, so long as any new problem doesn't force him to jump back to square one and abandon the solution

For his privacy I won't get into too many details about him/ what the project is/ the technical details, but feel free to ask questions and I'll try to answer as much as is comfortable. Since I have the insider scoop here, I won't be trading.