F1 2010 - output data to multiple devices?

Strange.

Dirt2 and F1 2010 have the same output mechanism, and EK had a working mechanism to extract data from Dirt2 and that mechanism worked along side X-Sim.

One has to wonder why he wouldn't use that same already working code instead of writting new code, and asking X-Sim users that have an SLI to get the data from his program rather than directly from the game. Why re-do the work and why do it in such a manner that it makes it more difficult for X-Sim users?

Am I missing something? I can do some testing as well in a few days.

I'm not really sure why he would do that either Berney. His proxy for DIRT 2 and F1 2010 is independent from the SLI Manager so you would not need to have an SLI to use it but it does not yet work with X-Sim.

@Martin,

I tested your latest Outsim plugin and it works perfectly with both DIRT 2 and F1 2010. I changed DIRT 2 and F1 config files to use port 20778 as instructed and the SLI Manager uses it's default port of 20777 now I can run both games with the SLI-Pro and X-Sim at the same time without any loss of motion quality.

Note.... You will need the latest beta SLI Manager 094d18c in order for the SLI-Pro or M to work with F1 2010.

Thanks Martin for sorting this out.

....Mike

So this is now working without the need for a 3rd party proxy? I hope so.

It would seem unfortunate for SLI owners to wind up with reduced motion quality (vs a standarard X-Sim solution) as the result of an unneeded proxy. We should only use proxies when there is absolutely no other choice!

Yes, it is working without the need for a proxy.


....Mike

Thanks Martin!
Great job!

Mike, ask EK why he decided to change what was working properly before (Dirt2)...

Cheers,

MY

I asked him but he didn't really answer the question.

Thanks Martin,

I'll do some testing with this tonight and let you know.


....Mike

Martin,

I finally got a chance to test the latest plugin and there are some issues with it.

1) It does work with the default settings of 127.0.0.1 port 20777
2) It passes through the data to the SLI Manager running on port 20778
3) The autostart feature does not work. I cleaned the registry of sender values and also made sure that autoscan was enabled
4) I do not use FSD's so I could not test this
5) Not sure what you mean by this one but I did not get any errors when closing the sender or plugin if that is what you are asking.

The main issue that I am seeing is that the profiler will stop at very brief intervals like I'm missing some data. This seems to be more noticeable when running in DX11 mode with F1 2010 but it also occurs with DX9. I removed this plugin and went back to the last one that you sent that is configured to listen on port 20778 and allow output to 20777 and it works without any issues in both DX9 and DX11.

I have not tested the new plugin with DIRT 2 only F1 2010.


....Mike

For testing #4, you can use the Commander.

Working on them now Martin. I need to verify that they will autostart when F1 is started. Will get back to you shortly.

Hi Martin,

Here are some screenshots of the tasks and processes running while F1 2010 is running. Is autostart supposed to work with the old DIRT 2 plugin by adding these settings for F1 2010? If so, it does not work.








....Mike

Just tested this. I have the correct entries in the Autostart entries, but the sender does not automatically change to the correct plugin when I start the game.

Window Name = F1 2010
EXE = f1_2010_game.exe

Thanks Martin,

I'll test this shortly.

The capital F was the problem. Auto-Detection works here now. I did not drive it though.

I just drove it briefly and it is working much better than the previous version and auto-detection is working fine for me as well after the change to the large F .

The data passtrhough to the SLI Manager is also working fine.

Will test further later tonight.

1) Tested OK
2) Tested OK
3) Tested OK
4) Tested OK
5) Tested OK
6) Tested OK, no more micro breaks

Tested with DIRT 2 and F1 2010

....Mike

Hi Guys,

I am having problems with this... I read the thread but cannot come up with a solution.

Problem is that both the motion and the Sli-pro work together, but the motion is not as good as it should be, or used to be, kinda jerky.

My system cannot be a problem because i upgraded my pc some weeks ago with a i7 - SSD - 6gbRam - W7 64bit, and now using my old pc for the profiler. (E6600 2.4 core2duo - 2gbRam - XP)

I used the latest multicast plugin and used 20778 in the hardwareconfig. Also cleaned the registry.





Am i missing something here?

Thanks in advance.

Rob

The plugin is working fine for me running on an i7 950 @ 4.1GHZ Windows 7-64 bit. I have the profiler and sender running on the same PC.

SLI Pro also works fine.

....Mike

Solved, after a new W7 install (my ssd failed grrr) it worked properly, so i do not know what the problem was.

After the F1 game update, native support is enabled. You can also use the Slipro app but you need to add a line in the hardware_config file to disable native support.

qoute EK:

ok change or add this line in ..\My Game\FormulaOne\hardwaresettings\hardware_settings_config.xml:

<led_display nativeSupport=true brightness=127 />


to

<led_display nativeSupport=false brightness=127 />

Sadly F1 2010 does not have sector times or other functions on the SLi, so i just use the native support from cm.

I have gotten the native system to work just fine, but the brightness is extremely low. I tried inserting the above mentioned <led_display nativeSupport=true brightness=127 /> into the hardware_config file, but it ignores and erases it as soon as the game starts.

Any ideas?