sky rendering

[alex25]

A third option would be to include position offset as 3 additional parameters per object in the objects/list.txt file. A long time ago there was a position offset but I removed it since it didn't seem that useful.

but that would mean adding three unnecessary parameters to the vast majority of objects. doesn't seem that efficient.

A fourth option would be to simply go into blender (or whatever modeling program you want to use) and move the objects around by those units.

I like the fourth option... having position offset data anywhere else but inside the model is redundant, and it'd require no change to the source. Is there any reason why this wouldn't work?

i don't like this option because it would mean redoing all the tracks, calculating the offsets, getting blender to actually do what i want it to do, etc. for what i had in mind, the changes to the source code would be minimal. your fourth option would imply a major rework of all the tracks i imported from rFactor (and if in the future one would want to change the position of the horizon it would mean going back to the original blender model instead of just editing a data file. on top of that the blender models are not publicly available. i might have them on disk, but that's just about it).

--alex--