top of page
North3.jpg

Course Build Process

Note: 50% of total cost due at beginning. Final 50% due when a playable “beta” course is ready to be sent. 

​

Process (2-4 weeks):

  • Potential client contacts designer to discuss course. After discussion, quote is given based on the base course build cost. Base course build includes driving range (if applicable), all things considered essential for an accurate course (such as bulkheads, fences, bridges, etc.), tree/vegetation across course, custom tee markers and flags (if desired), basic buildings and background objects. Extra levels of detail, custom buildings and background items may add an additional cost, depending on extent.

​​

  • Agreement is made and deposit is sent. At every step feedback is recommended and welcomed!

​​

  • Preparation: Course LiDAR data acquired, overlays acquired, and course terrain is imported into Unity. Designer sends client flyover of satellite and terrain data in Unity as designer talks through holes. This will look like a 3D earth rendering of the course.

​

  • Course Layout: Designer creates course splines in Inkscape, which becomes the overhead representation of the different types of surfaces on the course and is the basis on which the playing surface is created. Designer sends picture of this to client for review and for changes to be made. 

​​

  • Initial Course Creation: Using the splined Inkscape and OPCD tools, the course is created in Unity. Additionally, tees, pins are added into course. A hole-by-hole flyover, without vegetation, much editing, or any details added, is made for client to review. This will be similar to the first flyover but a little more robust.

​​

  • Detailed Course Creation: Designer adds detail to course such as trees, vegetation, coloring, buildings, objects, etc. and course moves toward playable beta. During this time communication will occur between designer and client for clarification on various things, as well as pictures sent to client. 

​​

  • Playable Beta: Once designer feels course is in a good spot for testing, designer will prepare playable beta for client. At this point final payment is due, and designer sends course to client for play, review, comments, update requests, etc. Playable beta is designed for additional feedback and updating of course. I consider this almost as a halfway point - meaning there will be plenty of opportunity for updates, changes, etc. after it is sent. 

​​

  • Continued Editing: Designer continues to edit course based on client requests and discussion. For many courses, this will take as long as the previous steps. Here the course is refined, fine-tuned, and prepared for final release. 

​​

  • Final Release: Once client approves, course is considered finalized and ready for release. Course will be released to public unless client specifies otherwise.

​​

  • Future updates: Various small updates may be needed if bugs are found during course play by client or others. 

​​

​​

Contact Jeff about a Course Build

Fill out the form below, email Jeff at jeffpruitt@mac.com, or find him on Discord at JPruitt10.

Thanks for submitting!

JPruitt10 Course Design (Jeff Pruitt)

bottom of page