Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
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.
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.
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.
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.
It would be pretty sweet to support it, since sometimes it's hard to see the needle.
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.
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.