Download Fps Creator Model Pack 53l
Tommye Hope
Besides myself anyone else think that the Rockstar Races are using more than 150 pieces? I struggle to build races with extras like Signs, Fireworks etc to flesh them out with because my tracks are using it up first. Transform races now will severely limit object dependent on what vehicles and transformations you add. I think we should get more model memory of at least 175 or even 200, thoughts?
I know, I know... not everyone has a super fast system (console or PC) and fast internets, but I think we're being limited for very stupid reasons. At least 200 to 250 would be easy IMHO, and that wouldn't melt too many platforms.
We now have 200 props which is good, however it is possible to run out of model memory before you have used up this many props. Model memory gets used up with various things such as advanced placement of props, use of dynamic props, fireworks, flaming hoops etc.
Using simple props you can easily place the full 200 props. I have found in the past that I can take for example a short stunt tube and place it with advanced placement/rotation options. If I repeat this using the same prop over and over, the model memory is little affected. However if each time I use advanced placement on a different prop type, the model memory gets used up quicker.
So if you struggle with model memory, try limiting your prop type variations. One little tip that may work if you're struggling for that last prop while out of model memory - save/publish the game, then exit creator and go back into it. You may find enough memory for the last piece.
Yup Nugsy, model memory only gets used for each new prop you use. Some props use a lot of memory but once you have used them once every further use has no effect on Model Memory. It it the same with adding Transform vehicles.
I started using Qt a couple months ago. It's been fine and easy to use. Last night I updated it and something messed everything up. I could not run qmake nor figure out how to fix it. So I uninstalled and reinstalled it. Now it is using the Clang model. I'm not sure if it was before but I don't think it was. Now the autocomplete is messed up. When creating the definition of a function in a .cpp file, the autocomplete won't fill in the parameters like it used to. Also, sometimes type names will become invisible. I know there are characters there, but I can't see them. And I can no longer Ctrl + Click a variable or function to hyperlink to definitions and things. Anyways. I would love to get rid of Clang and go back to what I was using before. I've looked everywhere, but can't figure it out. I am currently using QtCreator 4.7.0 and Qt 5.11.1. Help would be appreciated. Thanks.
Go into Help->About Plugins and uncheck the Clang code model plugin. You have to restart qt creator after that to make it take effect. I had the same problem when debugging a unit test. I was debugging code not in the project itself and it was dying repeatedly on me sending tons of kernel messages.
If you are using VC product then there are lot of components in eCat that can do this for you. If you want to use scripting, you can use component container and creator to first make the orange bottom, and then create each box and attach it and transform it where you needed it. But there are components and other ways to do this without writing code.
I managed to create the component with the Compnent Creator and also attached a conveyor to it. The difficulty was to adjust the coordinate systems(frames) so that the component is generated in the right direction. The frames of the conveyor were a bit messy as well, I just rotated and moved them according to my needs in the Modelling Tab and I hope this will not change them in the conveyor file, it should only apply changes to the file I am currently working in, I guess.
You say that I should create the bottom plate first and then create each block. I think I should avoid writing code for now since I am not completely confident with the program yet. A hint how to approach the problem without writing code will be appreciated.
I guess my mistake is that, when I made the component first I created the bottom plate and then all the blocks attached to the bottom plate and then moved across the bottom plate according to my needs.
Basically the bottom plate and the blocks are one component and perhaps this is what makes the robot grasp everything. By the way my detection volume is 50 mm while the height of the block is 200 mm, therefore the robot should not detect the plate, but since the blocks and the bottom plate are one components, the robot does grasp them together.
In the layout I attached in earlier reply, the sled and boxes are different components, and I am only creating the sled. The boxes are created with the sled because they were attached as child components, and then saved with the sled.
With hierarchy, it is like tree structures. And this topic has many roads to travel on. Basics are that component is created with its entire node structure, so if other components are attached to nodes in the component then those other components are also created. If you do not want that to happen, one solution is to detach the other components. And one thing to stress in component modeling is that geometry which should be considered its own product should be a separate component. As you mentioned, picking the geometry of component means the entire component is picked by the robot. If they are separate components, you can avoid that.
I wired a signal from the robot output to the conveyor belt motor, so that when the robot puts two plates with blocks on the conveyor, the conveyor is supposed to start. But look how the two plate get unaligned to each other. The offset is just as much as the width of one plate.
Basically I have a sensor in the end of the conveyor line which is supposed to stop the part(the blocks). The sensor works properly, it stops the blocks but the next blocks just overlap the first ones, I mean they do not stop behind the first blocks, they just overlap each other.
I am sorry for bothering you so much with my struggles with KUKA Sim Pro, but if you can suggest any kind of manual or any other documentation about KUKA SIM Pro where I read about all these commands and features, it will be helpful for me.
I tried to assign Length, Width and Height in the Property section, since I was thinking that the blocks actually does not have its dimensions assigned somehow as a feature or property but still the blocks overlap.
I was thinking about your suggestion about the Bundle Release Components, I actually do not pick the two plates with blocks at the same time. I pick the plates, along with the belonging blocks, one by one(one(1) orange plate with five(5) grey blocks on it) and then place them on the conveyor. Therefore your suggestion about turning the Bundle Release Components on probably will not work either.
What I could say now is that if I use only one conveyor the plates with the blocks stop exactly one after the other. I was also thinking if the problem could be in the conveyor settings namely the detection volume feature similar to the the gripper settings. Somehow the conveyor does not detect the object size when there are two or, perhaps, more components placed along the wide side of the conveyor.
Are you trying to do this? Without doing any scripting and using components from KS eCat, I program robot to place crates side-by-side, turn on conveyor, and then sensor attached to conveyor stops things.
Layout - Pick and Place Crates.vcmx (1.6 MB)
Yeah, I am trying to do something like this. I just want to keep creating crates until I reach a predefined amount which I count in the while loop. The crates are supposed to stop one after the other on the conveyor. Basically, when the first two crates are stopped by the sensor, the next two crates should stop just behind the first two crates and so on until the predefined number of crates is reached.
Perhaps it is a stupid question but why cannot I attach a sensor to a regular conveyor, it allows me to attach the sensor to the batch conveyor only? I do not see any difference between these two types of conveyors. In your layout you attached the sensor to a regular conveyor that is weird for me.
I figured out why I could not attach a sensor to a regular, straight conveyor. The reason was that the conveyor itself does not have the sensor interface in the behaviour section. I added Component Path Sensor behaviour, a Boolean Signal and a One To One Interface and now it works.
You can observe now the crates 1 and 2 move on the conveyor with Space Utilization turned OFF and they move as they are supposed to - next to each other. Then I turned the Space Utilization ON and crate 3 stopped just behind crate 1 but look where crate 4 is. It is at one crate space behind crate 2, it should be just behind crate 2, next to crate 3.
Yes, one suggestion is to use physics path in the out conveyor. The SignalActions property of the robot component allow you to release components to physics. Otherwise, you might need to do some scripting. Support or maybe others here can provide quick solution. If you share your layout with support, they can probably write a quick script for you, e.g. when signal from robot received, attach the components on path together.
I'm a member of a team of Technology Coordinators and Integrators (including Wendy Liska, Laura Busch, Mollie Heilberger, Dale Van Keuren, and formerly Jim Gonyo) in the School District of Waukesha, located in Waukesha, Wisconsin.
This team has been working for the past three and a half years to orchestrate the rollout and implementation of nearly 14,000 iPads to K-12 students in the district to provide the tools and access necessary to begin personalising instruction. Waukesha One, as the program is titled, is one of the largest 1:1 rollouts in the state and it is unique in that students and staff can personalise their devices with necessary and preferred apps in a self-managed model.
In selecting these apps, the team looked for apps that integrate well with Google Apps for Education, are flexible and not content/subject specific, promote thinking and doing aimed at the highest levels of Bloom's, are easy to use, and can output easily for publication to the world.
7fc3f7cf58