English Study Blog

New 3D programming project / < IT Comunications / < home /

Dialog 5

Short description:

A friendly, plain-language meeting about a 3D/VR project. Team members talk about tasks, time estimates, demos, and payment terms.

Team: Alice (Project Manager), Bob (3D Artist), Charlie (Lead Developer), David (3D Programmer)

Scene: Kickoff meeting to agree on goals and a rough schedule.

Alice: Morning, everyone. Let’s list the most important things for this VR project and set a simple plan.

Bob: Hi. I think we should start with good models and textures — that really affects how the VR feels. I’ll need time to make the main scene assets and characters.

Charlie: Looks matter, but so does performance. VR needs a steady frame rate. We should use level of detail (LOD) and other optimizations.

David: I can make a basic LOD system that lowers detail with distance. I expect about 10 days to build and test it.

Bob: For the main 3D assets, textures and basic rigging, I estimate about 15 days.

Charlie: For physics and interactive parts, plan about 12 days — setup plus tuning for VR.

Alice: And for animations?

Bob: Ten days for core animations.

David: If we add inverse kinematics (IK) for better hand interactions, add ~5 days. It helps users feel like they really touch objects.

Alice: So totals: LOD 10 days (David), Models 15 days (Bob), Physics 12 days (Charlie), Animations + IK 15 days (Bob & David). If we start next Monday, can we aim for October 15?

David: It’s tight but doable if we avoid extra requests.

Alice: Great. Weekly check-ins and clear milestones.


One week later — follow-up

David: LOD is working, but switching LODs in complex scenes costs performance. I suggest more optimization and occlusion culling — roughly 5 extra days.

Bob: I’m worried cutting polygons will hurt the look. Maybe we can rely more on textures and normal maps instead of removing a lot of detail.

Charlie: Good idea — use normal maps and baked lighting to keep visuals while lowering geometry. Let’s spend 3 days testing that.

Alice: Agreed. David, include that in your tasks.

Alice: Payment and scope: in past projects we had late payments and unpaid extra work. We’ll use milestone payments and write down any extra requests before doing them. Agreed?

Bob: Yes. Any extra work should be agreed and paid separately.

Charlie: Same here — clear scope and approval for changes.

Alice: I negotiated payments within 7 days after each milestone and a penalty for delays. I’ll also log requests so nothing is missed.


Demos plan:

  • First demo: LOD + basic models — show performance gains.
  • Second demo: Physics + animations — interactive scenes.
  • Final demo: Polished build with optimizations and fixes.

Who does what:

  • Bob — models, textures, animations.
  • David — LOD, benchmarks, optimizations.
  • Charlie — physics and integration help.
  • Alice — coordinate demos, notes, and client contact.

Alice: Let’s aim for the first demo next Friday. After each demo I’ll send notes and tasks. Thanks, everyone — keep logging extra requests so we stay on track.

Team: Sounds good — meeting ends.