fanlebowski
Registered
That was aimed more specifically at Tim and ISI. I know how the community makes them. If they want us to ignore the non lidar let them at least explain why we shouldn't worry.
ah sorry
That was aimed more specifically at Tim and ISI. I know how the community makes them. If they want us to ignore the non lidar let them at least explain why we shouldn't worry.
That was aimed more specifically at Tim and ISI. I know how the community makes them. If they want us to ignore the non lidar let them at least explain why we shouldn't worry.
ISI's Brianza is IMHO the best version available for rFactor. Looks really similar to real one.Monza has fewer elevation changes so maybe it's closer but nothing said it was perfect. ).
Is rFactor able to replicate such detailed surface, even if not scanned (randomly generated) and it's effects on handling ?
I've not done any track modding for rFactor, I've seen some comments from members who do and others perhaps taking educated guesses but maybe Tim can answer this. Its been mentioned that iRacing doesn't use the point cloud to make a detailed visible 3d surface but uses the additional data from the point cloud to create a layer that the engine 'reads' to calculate the effect on the car from the track surface. Is rFactor 2 capable of doing this or would any detail from the laser scan have to be translated into the 3d model therefore making the track very resource heavy.
... but rFactor 2 should be able to replicate believable track texture with random tiny bumps (not only big bumps), ...
That's because you keep teasing us with screenshots and stuff! Excitement for your product is a good thing, Tim. You should worry if people AREN'T asking you every day when rF2 will be ready! Not venturing into a possible business-expanding opportunity because people might be anxious about it's release doesn't sound like a very good reason--just the opposite.The average laser scanned track BUILD (not including the scanning itself) takes iRacing maybe 2-3 months. Are you prepared to wait? Because I think the #1 thing I read, EVERY DAY, is about things not happening a quick as people want them to happen.
There are plenty of businesses that are perfectly viable relying on licensing. Typically, there are two pricing options--exclusive use, and licensed use. Fonts, music, pictures, etc.--all sorts of media work this way. You could have a 'lower resolution' or 'out-of-date' (i.e. last year's scan of a track vs. this year's) that the average consumer would be quite happy with--at least knowing that sight-lines and major bumps and a more 'organic' surface (i.e. not sine-wavy) are present--and then the full-resolution, as accurate as possible version that the big players pay big money for. Of course, there is the possibility of lower-budget teams willing to subsidize the cost of the lower-resolution data as well. As I'm sure you're aware, it's not uncommon for companies to charge more for the same product just because it's used for commercial purposes. Take ISP's for instance. A business account is MUCH more money than a residential account--and probably slower speeds to boot--just because they can charge more because they know the business is making money off that internet connection.The comment above about not owning the data, that's the thing I thought was absurd.If someone comes to you, tells you they need a track(s) scanning and tells you they'll be using your software for their simulator. Are you seriously, even in your wildest dreams, going to tell them that you demand anything? That you want to have them pay you, and then you share their information out to everyone else (including their competitors)? If they don't want that information to be used by someone else, it's not going to happen, and totally contrary to being 'catastrophic management' it's actually why a company like ISI stays in business in the current economic climate. If you won't do the scan and keep it private, someone else will. And then you don't only lose the track scan, you risk losing the simulator contract, too. There's plenty of land surveyors and software engineers out of work right now who would be happy to pickup a nice contract.
Did you know that when ISI stopped working with EA they had to completely rewrite most of the engine? Guess why? Because they didn't own what was done while working for EA. That's how things work. Companies want work done for them, to be done ONLY for them.
+1I implore ISI to give it a try with one track. Test the waters--do Lime Rock-a nice short track with a lot of character. Some people will certainly buy it--I know I will.
But, when people talk about scanned tracks and how good they feel they tend to be referring to how bumpy it is in the sense of those bumps that you notice unsettling the car or moving it around - which might occur up to, say, 5 times a second at speed.
Well, a lot of people don't realise how varied the cambers are. This is the problem IMO with people saying that they can tell there's not much difference between this and that track based on vids, photos and possibly even driving on the LS track in some cases.
Hi Everyone,
I have read a bit of this thread, not it all (it's too long)
Basically I have been producing LIDAR race tracks now for the last 4 years for a number of customers.
I have been supplied side by side graphs showing the output of each wheel, showing the bumps from the real circuit and the bumps from the LIDAR circuit and they are very very close, it has to be otherwise the track would not be accepted! It's amazing really! I know that the data produced is used for car setups etc.
I think from a driving point of view it all comes down to your dynamic model that you are using and whether it makes use of the high density mesh that you are driving on.
Anyway if anyone needs a hand in generating a LIDAR track I am more than happy to help out.
Mark
www.markshires.com
(Don't forget to Facebook Like my page)
Ignore him mark. Some people don't quite get how a sensible forum goes. Any insite into your profession is a great help to this discussion.
If you don't mind me asking mark. What do you figure the Average cost of Lidar'ing a 4-5 km track with lets say a 3-10 cm accuracy would be? Assuming road surface only scans.
Even if you have an invisible higher detail mesh to drive on? (as in iR)Another point to make is that you wouldn't be able to run a 10cm LIDAR track inside rFactor it just wouldn't cope