10-03-2008, 01:36 PM
ArrayI don't know if you say the same in Portugal, but here in Spain we often say "Si alguien tiene hambre no le des peces, enseñale a pescar". That is, I think using a setup provided by someone else is maybe good for today, but not for tomorrow, as you're not learning anything.
I have some knowledge about rfactor setups and there's no secret: you learn by reading and testing, reading and testing, reading and testing...
In my opinion, I wouldn't like to share my setups with anyone outside the team, but I'll be willing to give some advices during the testing sessions to anyone who needs it. Of course, any team is free to publish their setups "open source" :bigsmile:, but I don't think it's a good idea for the organization to provide a base setup...[/quote]
My opinion too :) I don't know very much about setups, just some basic, but I test and try. If I notice something wrong on the car, ask someone to help me in what to change to solve the problem causing the bad car behavior, and I'm learning on that.
Sometimes I receive great setups and send it to some people, but only 1 or 2 specific friends and my own team. It's good for the time being, but not for my future. I've printed the Setup Matrix (a PDF document on the internet that explains the setups of racing cars, no only for rFactor) and I've learned a lot.
A base setup is not a bad idea, if it's only a little competitive, not for top spots, but at least to give the person a chance. But what I think would be great is to explain what is the best a car setup could be, in each specific track. I don't mean telling what to change directly, but saying something like "in this track the acceleration is more important, the longest gears, the grip, etc, explaining why, but not entering directly on specific setup and values for the setup. Something for us, who know a little or even some who know nothing, to become aware of what to do and why.
A person in a slow car which behaves correctly on track usually doesn't know what to change, just thinks it's himself that's not driving well. Sometimes, hints for those are welcome.
I have some knowledge about rfactor setups and there's no secret: you learn by reading and testing, reading and testing, reading and testing...
In my opinion, I wouldn't like to share my setups with anyone outside the team, but I'll be willing to give some advices during the testing sessions to anyone who needs it. Of course, any team is free to publish their setups "open source" :bigsmile:, but I don't think it's a good idea for the organization to provide a base setup...[/quote]
My opinion too :) I don't know very much about setups, just some basic, but I test and try. If I notice something wrong on the car, ask someone to help me in what to change to solve the problem causing the bad car behavior, and I'm learning on that.
Sometimes I receive great setups and send it to some people, but only 1 or 2 specific friends and my own team. It's good for the time being, but not for my future. I've printed the Setup Matrix (a PDF document on the internet that explains the setups of racing cars, no only for rFactor) and I've learned a lot.
A base setup is not a bad idea, if it's only a little competitive, not for top spots, but at least to give the person a chance. But what I think would be great is to explain what is the best a car setup could be, in each specific track. I don't mean telling what to change directly, but saying something like "in this track the acceleration is more important, the longest gears, the grip, etc, explaining why, but not entering directly on specific setup and values for the setup. Something for us, who know a little or even some who know nothing, to become aware of what to do and why.
A person in a slow car which behaves correctly on track usually doesn't know what to change, just thinks it's himself that's not driving well. Sometimes, hints for those are welcome.
