but atm there are no graphs, or ?

took i something wrong, but when i press the "Detailed Informations"-button for a racer in a race, a htaccess-popup with username and password appears and i only see the laptimes listed, but no graphs

you also can take a look to projects like this , everything you need to use gauges is available there or here is some package often used for simulator projects.

EDIT: http://www.x-simulator.de/foru ... car-instruments-t890.html

Last edited by haelje, Wed 27 Aug 2008, 10:19.

i tried to push it to the alpha-state, but the time was rare this weekend (or the work too much, it's a point of view ). i cleaned up a lot and did a avery important step to hold the users and teams in the db. i also extended the readme's and install-guide, but i'm not completly ready yet. if you wanna take a deeper look, visit the project homepage, there you find descriptions where and how to download the pre-alpha.
please report the bugs in the ticket-system, it's easier to handle for me and the tracking of problems works better imo.

http://liveforspeed.codemacher.de/trac/LFSWFramework/

EDIT: all the update issues are not checked completely, so in some combinations the update goes wrong.

Quote from sid6.8 :

ok!
2nd question:
The Memberstaus displays a German and an English Table... I want to display only the German one... What i have to do?

atm i dont know, what you mean with the english and the german tables, perhaps you can post a screenshot ?

it's not possible without changes with the original HoTTracker because it uses pubstat 1.2 and the splits for pb's is in pubstat 1.4. so you need to edit the parts (the db-structures need to be adopted too), or you give the new package a try, but without help atm it's hardly possible. i'll try to finish the install-scripts this month. you can download the current working-version here: http://liveforspeed.codemacher ... d_path=%2F&format=zip

to the last question: i think that should work. important is, that the execution of the php-scripts works correctly, so i think you can also embedd it into a html.

the fopen-error look like you didn't set the variable
correctly. there you should enter the full base-url, starting with http:// to access the file on your server.

Quote from Deejayyaj :

@ haelje:
I have a question...
Where do i put the ID-Key?
is it in this line of lfsworld.php?

take a look to the /includes/options.php-file, there are the variables you need to define.

Quote from Dygear :

If it's based on PHP, just hook into the LFSWorld SDK.

this is the plan with the version i try to develop from the HoTTracker. i did the adjustments to work with the new pubstat-version, but i'm not finished with documentation, so it's easy usable. in a further version all direct accesses to pubstat from the HoTTracker-base should be substituted to LFSWorldSDK, which is a very good package the time is rare atm, but in a upper post there is the link to the track of the project and you can checkout the current trunk-version with svn and give it a try. you also can you the trac to do bug reports and so on, so perhaps we should start to use it

if you took the original package, the first problem could be, that there are no write-rights for the webserver in the directory /data and the files inside. the tracker writes back data to that directory.

but if you say, that there is no content in the db ... mhhh ... atm i've no idea

[EDIT] ah, the biggest problem could be, that you need to adapt the lfsworld-request to the new protocol-version. i think the original package uses version 1.2. of pubstat, but atm there is 1.4 the current version. so the content changes and i dont know, if the tracker with the old version works correct, because of changes.

happy birthday from the whole 1stBFA-crew

noone is an idiot only because he doesn't know the specific effects of some graphic dependent settings the interface should provide a "newcomer-friendly" possibility to configure lfs in the right way corresponding to performance, anyway for the experts the detailed settings are perfect.

i hope it was not suggested anywhere, i did a search and can't find anything like this.

lfs has a lot of options influencing the performance of the game on a pc. with all the settings, i think you are able to find a configuration for slow pc's as well as high end pc's, but especially if you have an older, slower ones, it's a lot of trial-and-error to find the settings increasing the performance. finding these settings would be a lot easier, if there are some pre-selections. something like:
* best performance
* medium quality/performance
* best quality
so it would be easier to select a set of settings fitting to your hardware without knowing the consequences of every single setting. the improvement suggestion goes into direction of usability of complex setting possibilities. for beginners it would be a lot easier, if they are able to select the settings with such pre-selections. i know, there is a lot of information about performance settings in the forum and in the lfsmanual-wiki, but this will only reach the involved people. i mean some easy to pick settings, which definitly easy up the complex possibilities available in lfs.

makes sense, because you cann't deny the server-infos on lfsworld and so everybody, who is interested enough will find the results directly after the race (and the standings during it)

nice idea +1

Quote from Becky Rose :

The increasing number of sim racing series being broadcasted is interesting. There is more demand to create than there is to consume. Now that the emerging industry has saturated itself with so many productions at varying levels of quality before there was ever an audience I can't imagine the consumer is going to find it easy to get into the sport as a viewer. This was never a concern of most broadcasts as they're made with the competitor in mind, but for me its an area of grave concern and has been for some time.

Each broadcast produced is a showcase/ambassador for any non-simmer seeing the sport for the first time. If a broadcast or the series it covers is not designed to appeal to a new audience, then it is having a potentially negative impact on the sport.

For this reason i'm keaner now than ever to get my second series off the ground so I can replace my first series where I feel the quality was - well, "learning the ropes".

As for what to do about the market saturation, i've no idea... I tried to get all the broadcasters together into a union before to share ideas, skills, technology and expertise but, meh, they no likey the idea.

it's a very nice approach to see all broadcasts as summery to represent that kind of thing and you are totally right: a bad made broadcast is the worst promotion for lfs-broadcasts itselft. so it is very important to set standards, and if i understand you correctly, that's the aim you are going for, but noone wanted it like this ?
that's crazy, because all would profit of that. my first goal was to evaluate non-cost way to broadcast lfs, additionally some kind of software like TVDirector is neccessary to give all the information to the viewers.
the lack of viewers is really a problem and i think it can only be solved, if broadcasts are all available from a central place (like lfsvideo for videos), something like a lfs-boadcastTV with different channels.

for interested people: i started a trac-project-page for the tracker-extension i did with the HoTTracker-package. it's far away from a release (documentation of the install procedure is the most important part before going to a alpha version), but if anyone is interested to help developing that, take a look if someone wants to be in the developer-group, just PM or mail me.

http://liveforspeed.codemacher.de/trac/LFSWFramework/

i did not really continue this project until now, but i will. as a new start, i started a trac-page for the project, so i hope perhaps someone is interested in that we can use the ticket-system for any kind of question corresponding to the project, perhaps someone is willing to be a developer of this too, you only need to PM me or send me a mail.

i corrected the source links in the first post, so it points to the new trac

jep, thats the error. i changed it in the cfg.txt and it runs without any crashes. originally there is a 6 in my cfg.txt for antialiasing.

at first i need to say: TOP APP
i use it very often for watching races, capturing videos and screenshots. therefore i had 2 ideas came to my mind while using TVDirector:
1. for capturing purposes you often directly select the driver to watch in the GUI. with that you loose the focus of the lfs-widget and you need to change back if you want to do screenshots with the standard CTRL+S. so i would be a really nice improvement to have a button in the GUI which invokes the screenshot. dont know if it's technical possible to simulate that via Insim, if not through the idea away

2. for capturing it would be nice if you could force the showing of the driver-name of the currently watched driver, the same with rankings and time differences. so could it be possible that the user can invoke the different tables (driver name, time-table, pitstop-overview)? something like buttons and if you press the information is shown for a fixed time (like it is working now)

okay, here is the call stack. only to clear up: i can do the call of "LFS.exe /hlvc=xxx" in the standard command line ? if i start it this way a window like the dedicated server pops up and after that the crash happens.


EDIT: i have the MS Visual Studio installed and use the debugger of it, when lfs crashes. dont know if this gives you the same information drwatson would give, so i hope it helps

sorry for being so late with the answer, i use Y22-exe

i understand correctly, that i use the lfs.exe for that ? i tried and got an exception, perhaps this help:

EDIT: my OS is a Vista64bit

Quote from Scawen :

...

thanks a lot for that kind of preview information in my eyes it opens a path you will follow directing the usage of telemtry informations

1stBFA uses Typo3