[Plugin] Control points ver. 1.6.
-
I'm having no luck getting started with this. I suspect that I'm missing some changes in the directions for how to get started, but I'm pretty sure that I at least skimmed the whole thread.
- Download and install the v1.6 script from the first post.
- Open SU, create a test object (3D text my favorite for testing this kind of thing).
- Plugin Menu has four new items, but they all appear to need c-points already added.
- Right click (context click) on the group --
No new menu items, nothing mentioning c-points, the options suggested at various points in the thread (I don't know for sure that I've found the most recent) are not there.
Any pointers to what steps I'm missing?
Thanks,
AugustP.S. Windows 7, SU 7.1.6860
-
right click on a group (has to be a group)
-
@xrok1 said:
(has to be a group)
Thanks. I "thought" it was, but 3D text gets created as a component, not a group. Explode and regroup and the menu options are are there!
Thanks,
August -
got me the first time i tried this plug on 3dtext to solve your insane problem too.
(yes i'm still thinking about it.
) -
@xrok1 said:
(yes i'm still thinking about it.
)As I said, don't hurt yourself. I have a workaround.
For me it's now at the level of how to make these amazing tools even more insanely flexible while still keeping them intuitively useful. Maybe one of the extension ideas I throw out will stick to one of the developers the way this question seems to have stuck with you.
August
-
What happened to videos?
-
If someone still interested in this plugin, then, I guess, this video will be interesting too:
[flash=560,315:38wj9eza]http://www.youtube.com/v/dXHJSEXn86Y?version=3&hl=ru_RU[/flash:38wj9eza] -
Yep, the video is interesting. I may have to watch it another couple of hundred times until my little brain can fully grasp what all you did here.
-
@mitcorb said:
I may have to watch it another couple of hundred times...
200 views per one viewer, that's how I'll finally become popular on YouTube
in 'science/technology' category I mean
Actually I was trying to keep things simple, but it looks like I have to try more efficiently... Because it is still not obvious for end user, how everything works . The final goal is to make tool processing so intuitive that one would not need to watch tutorial 200+ times -
Well, you know I was joking. Actually, on a second viewing, and with more time to watch it through, the concept was clear enough. The details- commands, tool selections, sequence and so forth will take a little longer for me.
However, on one viewing, it is clear that this is a significant development. Congratulations.
-
Wow, amazing
Thank you
-
Great plugin. I look forward to create some terrain with it. But I have to confess I have some problems when I try to move the control power ... it is hard to me to focus the control point and it costs a lot of waiting till the red frame appears there. Sometimes I click, but it is too late, and the red frame disappeared so I have to remove the point. It looks slow for my computer even that my comp is not so bad on performance. I cannot to do it so fast as you do in demo video. Some key to remove node, for example backspace, would be very practical. I do it with context menu, which is slow. One more idea. It would be great if I could enter the power immediately whey I click on the terrain. I think that if I write the number in Measurement box, it does nothing... Also confider that that maps are done in different numbers. You have some terrain, for example altitude 700 and above. But if you add the power number to nodes like 700 or 725 and so on, so it will be too much for the terrain. To save the calculation for human, you could make one extra box, where user will write his base altitude like 700. Then he could write the number from a map and you would subtract the 700 from his number to get the correct number. So for example. I need to get these altitudes from the map to the terrain model: 712, 745, 765, 815, 922. I will enter value 700 as the base value. Then I create control points and I write to the Measurements box: 712 for first node, 745 for second node, 765 for 3rd node and so on. In the meantime the program will count: 712-700=12, 745-700=45, 765-700=65, 815-700=115, 922-700=222... And here are the correct sizes for my model... This is practical issue. Never mind if you would keep both values in the node...
-
Can somebody actually explain how to use this tool
- Move appears to be some fraction of the movement of the actual control point
- scale is not obvious but once you play around you get the idea, I see the intent although it too is a fraction of the actual scaling so again not sure the value
- etc
I tried playing with the power setting 0, 1, 3, 10....doesnt seem to make a difference
What I would have assumed this does is:
- Add some control points
- If I move / scale the control points, movement / scaling based on power
(ie if power = 1.0...then a 1:1 movement or scaling....power = 10...then 10:1...etc)
ya know, it would be good if a given plugin does what it says it will do
Some guys write solid plugins with good doc (Freddo)... others (to remain nameless) have
some plugins as advertised while others dont deliver even the basics (with some of them
appearing to be an exercise in ruby programming vs providing some actual useful function).Given this store idea....maybe somebody should have a clearing house on plugins to ensure
quality. Require good doc or (video would be fine but since the videos for this plugin dont load....pointless), ensure the plugin actually does its stated function, etcI guess its me....who knew that "affecting geometry" did not mean some sort of 1:1 relationship
-
One more thing. Since so many of these plugins are garbage and dont know that until have installed, the store (or a plugin) should have a feature that tracks how often a plugin is used. That way a user can clean up the garbage once a quarter or once a year
-
@vojo said:
Since so many of these plugins are garbage
You might want to consider that people who spent their time on these plugins offered them for free. They might not be perfect, they might not be doing what you had hoped what they do - but please show some respect.
-
@thomthom said:
- but please show some respect.
Thomas thank you for that
But actually vojo is right: it would be nice at least to mark (in some more or less obvious manner) things, which became obsolete. Erasing posts or attachments or any other erasing maybe an unsafe action, but marking is totally OK and it would inform a user an obvious way.
As for this particular thread, I edited the original post to inform people that it became obsolete and provided a link to a new thread and I'll do the same thing with all other obsolete plugins I posted here right now.
I think the good karma is to be responsible for what I've made no matter how I offer results of my efforts (for free or not) -
Kirill thank you for your efforts- very promising tools
P.S. I'd make your videos X1.5-2 times faster, будет намного веселее -
@rv1974 said:
Kirill thank you for your efforts- very promising tools
P.S. I'd make your videos X1.5-2 times faster, будет намного веселееThanks for your compliment!
Initially I used speed acceleration for some of demo-videos, but then I've been reported, that accelerated speed confuses viewer (even when I mention about acceleration somehow in video description). So I decided at last not to mess with speed of a footage in order to demonstrate actual processing performance.
It would be more funny if I'll make plugins work faster instead of making videos faster -
@kirill2008 said:
.
It would be more funny if I'll make plugins work faster instead of making videos fasterВерной дорогой идете, товарищ!
-
Krill....I did download thru the store but since one can not interrogate a script in RBZ format....I downloaded the old one to understand (buried deep in the code is a "pwr*3" statement which, on its face, would throw the whole thing off...ie. pwr= 1/3 might get somebody a 1:1 ration).
As far as my cantankerous tone, it really comes down to this "if somebody is going to dance, then they need to pay the band" Meaning if somebody writes a plugin (free or not) that does not provide the advertised function, then they should accept the criticism and scrutiny"
If a car mechanic offers to fix your car for free but instead really messes it up, are you happy since it was free???? No....free or note, you agreed to have the mech fix it. If I wanted to become an auto mech so I could fix it myself (since the other mech messed it up), I would. Sort of the whole fallacy of open source: Caters to the group the loves to spend hours tinkering with their car vs using the car to get somehwere to get something else done. I dont know about you guys, but even if I wanted to spend hours working on my car, who has that kind of time.
Advertisement