G27 RPM LEDs?

[Kherven]

Hey, I just got a new G27, and perhaps one of the more pretty, and useless, features is the lights on the wheel showing the vehicles RPM (It looks similar to whats on an F1 wheel( but like most games it doesnt work. Are there are mods/tweaks that would make it the LEDs compatible with ETS2? Its not a big deal, and is purely aesthetic, but I just thought i'd ask.

[zbobg]

Sadly no one seems to support the G27 LEDs.<-<-<- Now not true (May 2015).
LEDs can be enabled by using the fanaleds[www.fanaleds.com] plugin.

A long time ago in a galaxy far far away I remember there was (only) one game that did support the LEDs. But I couldn't tell you what it was now. It might have been DiRT 1 or one of the really old NFS games.

There might have been a Mod for the original GTR that had LED support.

I suppose the reason for no support is because the number of G27 users is really quite small. It's just another thing that uses up CPU cycles that developers have cut from games as the graphic engines get more complicated and use up all the available CPU resources.

[Ginnungagap]

works with F1 2011 ;)

[[Messerchmitt] Meerkat]

thats why i given up my Logitech G15 and went back to cherry g80-3000 LSCDE2

[necrosand]

Works in Project CARS, too. (Along with GT5)
zbobg:
Don't make some lame 'cpu cycle' excuse as to why the indicator isn't supported - what you're claiming is frankly not true at all and I would hate for new/uninformed users to be given false information.
The developer likely did not work with a G27 during the development cycle and simply doesn't know of the APIs Logitech provides to control it.

[Dinky]

zbobg님이 먼저 게시:

It's just another thing that uses up CPU cycles that developers have cut from games as the graphic engines get more complicated and use up all the available CPU resources.

Are you playing on a 486 or something? None of the features on these Logitech steering wheels should use a measurable amount of CPU time unless you've hit a glitch in the software or your system is about 20 years or more below the current minimum specs.

You should have just stopped at the bit about the small user base and left it at that.

[zbobg]

If you thought that the game developers don't know what Logitech has to offer in terms of technology then you aren't thinking. Logitech typically works closely with developers, Logitech DOES want developers to support their products.

Regarding: 486? 686? Pentium? Core 2?
This is a good point. Until recently (maybe before the last 2 years) the technology was in fact pushing CPU/GPU power to the very edge. Then there is the real issue of supporting low end hardware, particularly laptops which can be very low powered. There are a lot of folks out there with old marginal equipment that developers will still want in their user base, after all it's about selling a game not catering to a high tech niche audience.

By the way, I do have a rather old q6600 that runs games well enough but it is marginal by today's standards. My video is an EVGA GTX 570 OC which is quite adequate.

I mentioned the "CPU excuse" only because I have read that given as a reason by developers in the past. I agree that with current technology it's perhaps not now a valid reason. Today's CPUs, particularly the I5 and I7, certainly have a few cycles to spare but that was not always so.

[Dinky]

zbobg님이 먼저 게시:

If you thought that the game developers don't know what Logitech has to offer in terms of technology then you aren't thinking. Logitech typically works closely with developers, Logitech DOES want developers to support their products.

Regarding: 486? 686? Pentium? Core 2?
This is a good point. Until recently (maybe before the last 2 years) the technology was in fact pushing CPU/GPU power to the very edge. Then there is the real issue of supporting low end hardware, particularly laptops which can be very low powered. There are a lot of folks out there with old marginal equipment that developers will still want in their user base, after all it's about selling a game not catering to a high tech niche audience.

By the way, I do have a rather old q6600 that runs games well enough but it is marginal by today's standards. My video is an EVGA GTX 570 OC which is quite adequate.

I mentioned the "CPU excuse" only because I have read that given as a reason by developers in the past. I agree that with current technology it's perhaps not now a valid reason. Today's CPUs, particularly the I5 and I7, certainly have a few cycles to spare but that was not always so.

To be fair, they work closely with companies making games specifically geared towards their product. The only feature the G27 offers that other steering wheels don't (that ETS2 uses) is the H-shifter, and that isn't an API thing. They had no real reason to work with Logitech on anything, and even if they had, I'm not sure they would have really been a huge help since this is a really obscure simulator from an equally obscure company.

Anyway, the CPU cycles thing just wasn't relevant to this particular discussion. Yes, this has been trotted out a couple of times by developers, but under vastly different circmustances (most being console related).

No harm, no foul, the rest of the post was fine. It was just that particular bit that's now gone which was a little weird.

[michael.abon]

I really want this to exist. I might have to break down and make it myself.

[Jademalo]

It works with Dirt2 and F1 2012, but not Dirt 3. I always found that strange.

It would be pretty sweet to support it, since sometimes it's hard to see the needle.

[michael.abon]

Reporting in. Short story: not going to work from our end.

I downloaded the Logitech SDK and I unpacked the game archive. The modding support we have is limited to configuration values. That's why all the mods you see are sound, weather, lights, physics, models, and decals. Those are all values that the game just loads on start and uses as it normally would.

We want the game to do something it's not already doing. For that, we need to change the source code.

[zbobg]

It (is) might be possible to add the G27 LEDs, it's just not easy and probably not worth the time.

You would do this the same way you create a trainer. First you need to find the variable (a memory location) that represents the tachometer in-game, there's got to be one because the game does report RPM on the truck dashboard. Next you create a robust "trainer" that can hook into the game, find that variable, process it (in terms of scaling it) and send it to the API for the LEDs.

[Komfr]

We are planing to eventually add a telemetry output to allow external programs to retrieve information from the game. Some work was done on this however it is low priority.

[Ginnungagap]

rather have a better rpm display insted :) who needs a LED display that light up red all the time becorse you have 12 gear

[zbobg]

I would like to see the kind of API that MS supplies with FSX. A list of internal variables and a simple method to access them using a programming language such as any of the free MS compilers available with Visual Studio. Or you could go really simple and provide a LUA interface Like GTA IV.

[michael.abon]

Super excited to hear that, Komfr!