Quote:
Originally Posted by Taz D
I just used the Buy multiple in the menu for a tree and keeping the mouse pointer in one location was able to place 5 trees in the same spot. This is how the count gets off from what we think it should be. The only way you will see them is by moving them to another location.
For the ones who have some show back up as ready after you know they have been harvested maybe some that are inadvertently on another layer. Some have seen that with crops where they show back up or a plowed field shows up after planting.
|
Taz, for the most part, you are correct here. The count is off due to multi-trees on the same x,y lock-point. If Trees are on, then in most cases, all the trees will show but the viewer will put one on top of the others so it becomes not seen if smaller. I have a stack tree farm with an Fruit, Oak, and Pine on each lock-point for half a map. since pine and oak are chop, the dim works and show both oak and pine when chain saw or axe is picked. Once the pine are axed, the oak can be seen and axed and the tool works on the fruit as it was the first down on the grass. This 'First down rule' can be altered if you know how or is able to 'freeze' the load so only the pine or if the pine and oak loads, tool works on oak, and on pine where there are no oaks under them. AS Slashkey learns more on flash, and if they can use a 'load only object' the tool would work on all objects.
Trees and Flowers also tends to get stuck to other objects on the same X,Y lock-point and can disappear when they get stuck to buildings, deco, seasonal objects that are toggled off. The tool Selector (yellow highlight) can not click on item not there in the viewer because the viewer hide the item and is showing buildings over solid tree layers. This is why most love the Dim - w/ hidden selected. They are more apt to get full loads (all the data in the file) when hired or working their own farms.
I have also noticed that it is a load issue (server not sending all the data in the file) when the notes do not open. I find that the notes fail more when the images on your neighbor bar do not load.
The fast click or shaky fingers when using the buy multi is the cause of more then one of the same tree placed in the same x,y lock-point. However, since Z is assigned by FLASH, the x,y,z of each tree is different. The viewer may only show one of the objects but may show say pine, after one has been chopped. The next one may need to be chopped with axe as it is not the first down on the grass.
"Come back crop issue:" With Oats, Hops or Barley, the reason these come back is due not to the file or viewer but due to the properties of the object. The fact that these act differently from the other crops are proof of this. Other crops have 'crop with bar issue' where the bar (0%-100%) are also an object properties issue. Most of these are first generation crops from day one. Yes, these two issues are worst for those pros who offsets and place pods (plots of dirt - fields) on each x,y in a 9x, 3x or other overlaid layout.
And remember, AN OVERLAID LAYOUT CAN STILL BE LAYERED AND GO X DEEP.
Flash has limits. One limit is the total number of objects allowed in the file before the data is sent to trash can. This is counted to be ~35,000. Adobe does not list this in their developer manuals. Same with how many Z axis flash will assign before sending those objects to the trash can. FLASH is like any other CAD program, both controlling the front to back on the viewer, and the grid is an x,y,z grid.