I haven't used them, but they are probably dummy props. Try Control+D, which toggles dummy visibility.

---

As to the trees, I just tried the Monterey Cypresses, and they show up OK.

I also saw the change in timestamp. I believe this is related to iClone 7 having to do some conversion to load the tree; I've seen similar happening in previous versions.

EDIT: My driver version is 385.41.

---

The purchased Speedtrees seem to be working for me as well. As Job mentioned could be a driver-display issue.;)



Click here to go to my YouTube Channel filled with iClone Tutes and Silly Stuff

Visit ANIMATED PROJECTIONS Powered by iCLONE

Intel Core i7 3960X @ 3300MHz Overclocked to 4999.7 MHz Sandy Bridge 24.0GB DDR3 @ 833MHz Graphic Display HP ZR30w 
GeForce GTX 980Ti 6GB  Microsoft Windows 7 Professional 64-bit SP1 ASUSTeK COMPUTER INC. P9X79 WS (LGA2011)

I have and am currently experiencing the dissapeared speedtree issues.

https://forum.reallusion.com/335614/Total-Plants-Collection-Issues

They show up with the placement brackets only.  No trees.  Then they randomly come back.  And then dissapear again.  This is my second iteration  Updated driver to no affect.  After some back and forth with RL they blamed my system but I think enough people have experienced this to say its a bit bigger than that.  Bezzer has experienced this as well as noted on the IClone users facebook page.

This is not your system, this is consistent with a bug.  iC 7.1 is not optimized yet.
I just tried updating the Nvidia Driver to 388.11, with 7.1, no dice.

Then I uninstalled iC7.1 to test a reinstall....
BUT....While I was reinstalling, I had to install 7.0 by itself, and then proceed on to 7.1.
So I tried Speedtress while in v 7.0...take a guess what happened...
IT WORKED. 
No driver conflict, no system glitch, none of that.  They loaded in and worked!  This is 10 minutes ago...  

Then I proceeded to install the 7.1 update, but now again they do not load in.  
So not a driver issue, not a system issue, no.  It is a bug in 7.1, clear and simple.  Now do bugs affect all systems same, maybe not.  But the bug is there. 
It can't be a driver issue if I can install 7.0 and 7.02, and it works, and then 7.1 it doesn't work.
That's like saying 7.1 revealed the issue we really had, but before that, we just did not know it yet....does this make sense.
Now, if in a predictable and repeatable fashion, one can say, you now need to upgrade driver to 38x.xx...etc, in order for SpeedTree to function, then that ids different.  But this is not the case, no one knows, in a repeatable and predictable fashion, what driver 'fixes' the problem.  More consistent with a bug in 7.1.

But RL can and will fix this BUG!

I know that this doesn't help those having the Speedtree issues, but I can't reproduce it on my system - sorry guys. :ermm:

Gerry

---

System: Win 10 Pro (21H2), Asus X99-E WS, CPU i7-5930K -3,5 GHz, 32 GB DDR4 2666-16 RAM, NVidia GTX 1080 Ti GPU - 11 GB VRAM(Driver Studio-536.99), Samsung 850 Pro 512 GB SSD, 6 TB HD storage.

The issue was affecting me (and I believe Bezzer as well) in 7.0.  I haven't tried it since upgrading to 7.1

Can you advise on what specifically it was that they blamed about your system?  Was it Windows version, driver, etc.
Sounds like they know exactly what it is that is causing this if they know that it was your system.
I'd like to test different variations of what they said would be the cause in my system!
Thx!

I notice that this somewhat sporadic, but serious, Speedtree issue hasn't yet been added to the Feedback Tracker by any of the sufferers. I wouldn't put too much hope on any (RL) type reading this thread and doing anything about it, but they do read and react to issues logged in the FT.

Gerry

---

System: Win 10 Pro (21H2), Asus X99-E WS, CPU i7-5930K -3,5 GHz, 32 GB DDR4 2666-16 RAM, NVidia GTX 1080 Ti GPU - 11 GB VRAM(Driver Studio-536.99), Samsung 850 Pro 512 GB SSD, 6 TB HD storage.

Gerry's right.  Not only that, but my trouble ticket to RL was dismissed by Peter because they couldn't reproduce the issue, so I have ZERO doubt no one is working on it or even thinks it IS an issue yet.

If I hadn't seen it for myself I would have doubted it as well.  And an issue they can't reproduce is an issue they can't fix, so even if they see it listed in the tracker don't be assured anything will come of it.  What has to happen is for someone to be able to get RL to see it, not that someone can produce it on their own system.  So what I would do is put in a trouble ticket first, and carefully outline your computer and system specs and work with Peter at least to see if something can be done on the RL end to actually SEE the issue.

Also, with a file that doesn't work for you, post the FILE here and let others load it in.  If it loads in correctly, then it's not a bug with iClone per se, but more a system issue dependency (for example, while it isn't in this case, it could have been a video driver issue.  Or perhaps a Windows version issue.  If the same saved file works on everyone else's computer but not on yours it can't exactly be ONLY an iClone program issue).

I am not at all optimistic this one will get solved.

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley