I really wouldnt know about that, but since Dygear said that Windows was skittish on Java, and not the other way around, I figured it was Microsofts fault.
Then the guys from microsoft shoulg get their act toghether and make sure my program runs on that platform.
I dont think I am using any fancy stuff, so if my program doesnt work, then I dont think any program except form the Hello, world! will work.
The last race saw a lot of new teams, and some of them were planning to race in the upcoming events. Because I have not kept track of all the plans and intentions (and because plans can change) I ask all the teams to post here if they want to race in the next 6h race. Also because some teams have the capability to enter a secondary team (since the race is short, 3 drivers per team should be enough) it is important to know this well ahead of the event.
If a huge number of teams want to race, we might increase the limit of 15 teams.
Current starting list
tHUNder Racing
ITEK Racing
teamnic
MasterBlasters eV
Estonian Endurance Racers
Shock.fx
Pedal to the Metal
HFD
Cyber Racing
Ocrana 1
Ocrana 2
POD
n!faculty 1
n!faculty 2
NB: the order of the list above doesnt give you any rights whatsoever
I guess it would be easier to just simulate a force, rather then creating some code that allowes you to artificially move the cockpit, while it actually isnt moving etc.. If you are able to simulate 4 tyres and downforce, it shouldnt be too hard to apply a moment somewhere on the car that is proportional to the rotational speed of the engine.
-moving : these cameras will automatically zoom, rotate and pitch according to the position of the car you are looking at relative to the camera.
-non moving : these cameras will just look in a certain direction and not move in any way.
Actually the name 'moving' is wrong, because neither of the cameras are actually translating. Translating cameras will be investigated tho (Im 90% sure it will work).
The camera positions are stored in an external file, so you can make these files available for download.
EDIT:
I think I see now what point you are missing The program cotrols the camera, but the userinput is the player to look at. You will see a list of buttons, all representing a player, you press one button, and the program will follow the car around the track.
I havent done any tests with this yet, but I dont really understand. First you say that you can set the Roll value using a CPP packet, and then you say you cannot control the Custom view camera with InSim...?
Oh, and the FOV can be put lower then 12 and higher then 120. Everything between 0 and 180 degrees will work, except 0 and 180 themself. I think that the values serve a reason however, because some graphical glitches will occur between 0 and 12, and 120 and 180. So for a moving cam I dont think going lower then 12 is smart, but for a static cam you can easily use 2, as long as you place the camera on a 'smart' place.
At the moment the program predicts where the car will be in X milliseconds, since the camera will take some time to move fluently to that position. At the moment it only uses the heading, velocity and the current xyz values, but I think that some improvement can be found in the Angular Velocity field, and also taking the first and second derivatives of the xyz values can maybe help too.
As for the 'interesting-moment-prediction':
I think it is impossible to have a really good realtime predictor. I think you can make something that works well but not really good. However if you would store all the MCI packets in a separate file (with some sort of timestamp) while watching a replay the first time, the program is able to look into the future the second time you watch the replay. For replays a lot of people are going to watch, one person could take the noble task of running the replay the first time, and then send the 'prediction-log'-file to the other people who want to watch the replay.
Currently it works with one file called cameras.txt which houses all the cameras (so it's not hardcoded into the program). I will most likely change that to a system where you have a file for each track (or each area of tracks), so you can manage the camera settings yourself.
What is noobTV?
noobTV is a tool that allows you to control the camera in LFS from outside the game. It also adds the possibility to use and define custom camera positions, which will have more features than the standard camera's in LFS. It is written in Java, so you will need the Jave runtimes you also need to display some content on websites. The program will look like a generic Windows program, with some buttons (at least one for each player) and a few lines that display the current status of LFS and the tool.
The main reason for this tool is that I think the regular LFS camera's don't show a good overview of the cars on track. Also the number of camera's is in my opinion too high, meaning that the camera is constantly switching, especially on tracks like South City.
How can I use it?
The program is intented to be connected to a local LFS game, with LFS in windowed mode or with LFS fullscreen and the tool on a secondary display (secondary monitor, like a tv). It should also be possible to run the tool on a different pc (such as a laptop) as long as that pc is connected to the LFS pc via LAN (since the network load might be heavy and loss of packets will make the image less fluently).
When will I be able to download it? Look further in this thread
I dont understand what it does
Because images say more then a thousand words, here is a little video clip for you. I told the tool to focus the camera on the yellow/white car (someone from the Z30 team) while it is driving around Blackwood. All the camera movement/placement is controlled by the program, I didnt pause LFS to move the camera or something You see that the camera positions are different from the ones originally in LFS.
Click here to download the movie.
What are the current features?
Check out the readme
I will use this thread to keep you informed on the tool untill I release it (then I will post some thread in the LFS Add Ons subforum).
I dont think the gravity model of rFactor is wrong. I think the mass, or massdistribution of the rFactor cars is wrong. I recall reading something about massdistribution for the porsche cars in rF. They were not realistic, but did provide a realistic Porsche-handling. The discussion was wether this trick was a bad or a good thing.
But it could also be just a bug when a car is at some special spot. Maybe the gravity is correctly modelled when the car is on track.
That was one of those 'fill in your own text and get a picture' scripts. It would let you type any text and it was placed on top of the sign. I believe the original sign said something not very nice...
If you pm me your email (preferably an adress that can take large files), or even better the logindata for an ftp, I could zip all the parts I have and send them over. I should have the start and the finish at least, and some parts in between.