| Redisplay Messages: Compact | Brief | All | Full Show Messages: All | Without Replies Author: | Nubs_Select | Posted: | May 18, 2023 22:45 | Subject: | Re: Ridiculous amounts of spam on forum | Viewed: | 59 times | Topic: | Off Topic | |
| probably a teen dropshipper who sold something once thru 1 link and is now spending
all his time spamming until he sells something again
|
Author: | BricksOfFaith | Posted: | May 18, 2023 22:43 | Subject: | Ridiculous amounts of spam on forum | Viewed: | 281 times | Topic: | Off Topic | |
| Anybody know why there has been so many spam messages/scams on the forum the
past few months? It’s getting kinda irritating….
|
|
Author: | Stellar | Posted: | May 17, 2023 15:32 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 44 times | Topic: | Off Topic | |
| In Off Topic, macebobo writes:
| I took my time to report an error through the Report a bug or technical issue
link
https://www.bricklink.com/helpDesk.asp?helpDeskID=114
and only after one day I got this back.
| Thank you for contacting us.
|
| For all API-related questions and suggestions, please contact our API Department at apisupport@bricklink.com.
|
They could not even forward it themselves and then let me know that I needed
to report issues there!
Ugh! I guess I am going to start calling them the less than helpful desk again.
|
Hello Sergio,
Thanks for reaching out to us.
We had a few users make us aware of this mistake and appreciate you letting us
know as well. We have passed the information on to our API team, and they are
currently working on getting this fixed.
Thank you again for making us aware of this, have a wonderful day.
Just got this reply to the same issue that I too opened a ticked, seems our concerns
got in.
|
|
Author: | SylvainLS | Posted: | May 17, 2023 12:51 | Subject: | Re: Stud.io lagging with large builds. | Viewed: | 30 times | Topic: | Related Software | |
| In Related Software, Leonidaz writes:
| So I'm currently building a large map about 200 by 300 studs in size and
stud.io always freezes when I move, copy or add pieces. I've read that putting
the 0,0 coordinates into sight when building should resolve the freezing and
crashing, but at the moment it freezes regardless of what I do and eventually
crashes.
There has to be something that's being calculated or something in the background
that causes the program to overload, but I don't know how I could prevent
this from happening. I've tried 30 and 60 fps options, colission off, but
both didn't help.
Does anyone have had similar experiences or ideas how to fix this
|
Hi,
The dedicated forum for Studio and PartDesigner is https://forum.bricklink.com/
(hover over the red Studio icon on every page, then click “Studio Forum”).
Please search the forum for your question before posting a new one (the search
box is in the very dark grey banner).
There’s indexes of known bugs and suggestions that you can browse first:
Studio: https://forum.bricklink.com/viewtopic.php?f=4&t=5579
PartDesigner: https://forum.bricklink.com/viewtopic.php?f=10&t=5589
The main threads talking about the problem you’re experiencing are those:
https://forum.bricklink.com/viewtopic.php?f=4&t=7614
https://forum.bricklink.com/viewtopic.php?f=4&t=7624
https://forum.bricklink.com/viewtopic.php?f=4&t=8059
https://forum.bricklink.com/viewtopic.php?f=4&t=8322
|
|
Author: | Leonidaz | Posted: | May 17, 2023 12:39 | Subject: | Stud.io lagging with large builds. | Viewed: | 53 times | Topic: | Related Software | |
| So I'm currently building a large map about 200 by 300 studs in size and
stud.io always freezes when I move, copy or add pieces. I've read that putting
the 0,0 coordinates into sight when building should resolve the freezing and
crashing, but at the moment it freezes regardless of what I do and eventually
crashes.
There has to be something that's being calculated or something in the background
that causes the program to overload, but I don't know how I could prevent
this from happening. I've tried 30 and 60 fps options, colission off, but
both didn't help.
Does anyone have had similar experiences or ideas how to fix this?
|
Next Page: 5 More | 10 More | 25 More | 50 More | 100 More
|
|