|
Post by dmasewindu on Jan 11, 2021 17:57:58 GMT -5
Hi all, I am new to using LIDAR and recently loaded a pretty cool piece of land I found into the game. I don't have any objects on the course but I can't do anything or publish it to work on it in 2K21 because I keep getting a notification that I'm exceeding my object limit and need to remove objects to keep working on it. Does anyone have any idea what the problem is? I tried to search around for a similar thread and couldn't find one, so please pardon me if this question has been asked and answered previously.
Thanks!
|
|
|
Post by sandsaver01 on Jan 11, 2021 18:53:49 GMT -5
Hi all, I am new to using LIDAR and recently loaded a pretty cool piece of land I found into the game. I don't have any objects on the course but I can't do anything or publish it to work on it in 2K21 because I keep getting a notification that I'm exceeding my object limit and need to remove objects to keep working on it. Does anyone have any idea what the problem is? I tried to search around for a similar thread and couldn't find one, so please pardon me if this question has been asked and answered previously.
Thanks!
I can only surmise here: two things; is the plot really full of elevation changes, or are you trying to bring down lidar that fills the entire square area in the designer? if it is either or both of those, you will have to mask off a lot of the area that will not contain the actual golf holes. I hope that helps, otherwise I have no clue.
|
|
|
Post by dmasewindu on Jan 11, 2021 20:15:55 GMT -5
There are a lot of elevation changes, but nothing too crazy (about 150 feet at most) I did have two sides that’s came all the way up to the edge of the plot, so that might be what it is. I’ll have to do some more with the mask and see what happens. Thanks!
|
|
|
Post by yeltzman on Jan 12, 2021 5:54:16 GMT -5
Check your course file size in your courses folder looking at anything from 4000kb to 10000kb to play decent on console,Smaller the better.It seems to me the flatter the terrain the smaller the file.
|
|
|
Post by sandsaver01 on Jan 12, 2021 6:32:40 GMT -5
There are a lot of elevation changes, but nothing too crazy (about 150 feet at most) I did have two sides that’s came all the way up to the edge of the plot, so that might be what it is. I’ll have to do some more with the mask and see what happens. Thanks! A lidar elevation change of 150 feet is quite large actually. Elevation changes you make using the sculpting tools don't affect the object count hardly at all, but Lidar elevations do. I worked on a course in Nevada called Cascata, and it had terrain like that, eventually I dropped it because of the meter filling up.
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Jan 12, 2021 8:13:49 GMT -5
First of all there is a bug in the 2k21 designer when importing tgc2019 course files. It will state that you have maxed out your object meter even when you are at 50%. When you make the course in chadstool, import into tgc2019 and delete a tree. If you haven't imported trees, mark a single tree in OSM and import OSM trees when you build the lidar course. If you are attempting to go straight from chadstool to 2k21 while bypassing tgc2019, you should still be able to open the file in 2k21 (after using the python script) and delete this single tree and have the meter drop down to where you can work with the course.
The object count is correlated to drastic and steep elevation differences within a few surface square meters. Since most people will select plots much larger than needed when building fantasy courses with lidar, there are a few things you should do.
1. In OSM create four fictional fairways that mark the "boundaries" of the course 2. Select a smaller area (Red box around your fictional fairways) when processing the lidar heightmap (delete these fairways from OSM once done with this step) 3. Generously mask off any area that surrounds your working plot 4. Consider processing the lidar map at 4.0 (instead of the default 2.0) resolution. This will result in softer elevation transitions (and a much lower object count), but since this is a blank slate, you can re-sculpt any land features you desire. 5. Do NOT import lidar trees into a fantasy course. This will max out even the smallest undeveloped lidar plot. 6. Use autogenerated terrain features set to maximum (trees) . Lay out your course with "remove generated terrain brush." 7. Create a masterpiece.
Further notes:
File size (not object meter) is related to plot size, the bigger your plot, the greater the mask amount you need to do. I wouldn't worry about this for a fictional course if you follow the steps above.
Theme choice can impact object meter. Pine trees are horrible meter eaters. Use the Countryside, Delta or Desert themes to create the course file and continue with while working (Desert also shows the most terrain surface detail which is fantastic for plotting) as these don't impact the object meter as much. Once done with the plotting and golf elements, switch to theme of choice and begin planting. If concerned about how well the course will play on consoles, try to only plant objects from the chosen theme.
Lidar imported terrain uses the BLUE sculpting tool. The blue tool impacts your object meter. Soften or flatten areas where the high resolution terrain isn't needed. Or if you have a terrain hole, fill it with water (this lowers the object count).
150 feet isn't much actually, the issue is when there is a vast amount of surface area with constant 150 elevation changes (that are visible), meaning sheer cliffs like what you may find in a quarry. These types of terrain features are simple to work with if you follow the steps outlined above.
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Jan 12, 2021 8:16:42 GMT -5
Check your course file size in your courses folder looking at anything from 4kb to 10kb to play decent on console,Smaller the better.It seems to me the flatter the terrain the smaller the file. 4kb is the size of this post you made here on the forums... I think you mean 4MB to 10MB which translates to 4000KB to 10,000KB. The case of the K and M matter too. Plot size rendered at 2.0 resolution is the direct correlator to lidar course file size. For old xbox, 6MB and smaller files are recommended.
|
|
|
Post by yeltzman on Jan 12, 2021 11:13:39 GMT -5
**** changed my post with the right KB size****
Rye (old) was 9,356 KB and it takes a while to load on the old xbox but it plays and you can have a 2nd round without crashes.....but like you say recommend around 6000 KB to be sure.
Unless the file is really massive most will load, but sometimes they crash when you try to play a 2nd round on the old xbox.
|
|
mal
Amateur Golfer
Posts: 214
|
Post by mal on Jan 12, 2021 11:57:22 GMT -5
**** changed my post with the right KB size**** Rye (old) was 9,356 KB and it takes a while to load on the old xbox but it plays and you can have a 2nd round without crashes.....but like you say recommend around 6000 KB to be sure. Unless the file is really massive most will load, but sometimes they crash when you try to play a 2nd round on the old xbox. Rye (old) is fantastic by the way. Love your stuff. I don't have a Switch, but I'd be curious about how well/poor some of these courses play on that system. My greatest file size is currently 8.22MB and that is a fantasy course built on lidar terrain of an active quarry. I had to scale the plot back some due to results from playtesting on xbox.
|
|
|
Post by dmasewindu on Jan 18, 2021 20:38:41 GMT -5
Thanks for all the help everyone! I think the terrain I picked was just a little bit too treacherous to work well
|
|