Race Sim Central
Rec.Autos.Simulators Archive

RBR - don't buy it - yet...

35 posts by 17 people · 17 Sep 2004 12:18 UTC - 19 Sep 2004 20:45 UTC

RBR controller support versus Papyrus calibration

Kendt Eklund warned users with non-standard controllers not to buy RBR yet because of reversed brake axes. Posters shared DXTweak2 workarounds and argued whether the fault lay with high-end wheels, DirectInput or developers, with many praising Papyrus's own calibration routines. A side argument arose over Steve Simpson's claim that RBR beat NR2003 in physics.

tech supporthardware: wheels/pedalsgame comparisonRichard Burns RallyNASCAR Racing 2003 Season

Automated summary.

Kendt Eklund 17 Sep 2004 12:18 UTC#31910
IF you have any non-standard controller setup, that is. My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is recognized, but the damn brake is reversed and nothing I try seems to fix it. For a sim targeted at high-end users, they better cobble a patch together. Sounds like a lot of people w TSW/ECCI gear have the same problem. Kendt
AD 17 Sep 2004 12:24 UTC↳ reply to Kendt Eklund#31914
I had the same with my Act Labs but cured it with DXTweak 2 by just clicking the brake axis and then Axis Defaults then apply then started the game and went into controllers and assigned as normal..it took a bit of working out but as along as no other axis were touched in DXT2 it was perfect. AD "Kendt Eklund" <[email hidden]> wrote in message news:[email hidden]...
Quoted text (11 lines)> IF you have any non-standard controller setup, that is. > > My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is > recognized, but the damn brake is reversed and nothing I try seems to > fix it. > > For a sim targeted at high-end users, they better cobble a patch > together. Sounds like a lot of people w TSW/ECCI gear have the same > problem. > > Kendt
Quoted text (9 lines)> IF you have any non-standard controller setup, that is. > > My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is > recognized, but the damn brake is reversed and nothing I try seems to > fix it. > > For a sim targeted at high-end users, they better cobble a patch > together. Sounds like a lot of people w TSW/ECCI gear have the same > problem.
What's the deal with all these so-called high-end controllers? Do they not have proper Direct X driver support for split axis pedals? The only games they seem to support are Papyrus games which use a proprietry controller routine. It's the same old story with every game release. Game developers have to fudge their controller routines just so that they work with the outdated drivers for these things. Sorry if I sound like I'm moaning but I'm getting really sick of this every time a game is released. :-\
I've always said Papy (& their heirs, assigns & successors) could make a fortune licensing: 1. Their physics engine. 2. Their controller algorithms. 3. Their replay routine & UI. But noooooooooooooooooo............ "Steve Simpson" <[email hidden]> wrote in message news:[email hidden]...
Quoted text (11 lines)> > IF you have any non-standard controller setup, that is. > > > > My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is > > recognized, but the damn brake is reversed and nothing I try seems to > > fix it. > > > > For a sim targeted at high-end users, they better cobble a patch > > together. Sounds like a lot of people w TSW/ECCI gear have the same > > problem. > > What's the deal with all these so-called high-end controllers? Do they
not > have proper Direct X driver support for split axis pedals? The only games > they seem to support are Papyrus games which use a proprietry controller > routine. It's the same old story with every game release. Gamedevelopers > have to fudge their controller routines just so that they work with the > outdated drivers for these things. Sorry if I sound like I'm moaning but > I'm getting really sick of this every time a game is released. :-\ > >
> I've always said Papy (& their heirs, assigns & successors) could make a > fortune licensing: > > 1. Their physics engine. Not these days... > 2. Their controller algorithms. ..which are non-standard and are basically the main cause of the current mess. > 3. Their replay routine & UI. yes, definitely.
Steve Simpson 17 Sep 2004 13:06 UTC#531978
Not these days... ..which are non-standard and are basically the main cause of the current mess. yes, definitely.
Steve Simpson <[email hidden]> wrote in message news:[email hidden]...
Quoted text (15 lines)> > I've always said Papy (& their heirs, assigns & successors) could make a > > fortune licensing: > > > > 1. Their physics engine. > > Not these days... > > > 2. Their controller algorithms. > > ..which are non-standard and are basically the main cause of the current > mess. > > > 3. Their replay routine & UI. > > yes, definitely.
Exactly. > >
The N2003 physics engine still beats anything out there, IMO (altho GTR's is getting closer and closer). There are no controller standards. Papy's calibration routines have always been bulletproof. I forgot 4. Their multiplayer code. Still the best, IMO. "Steve Simpson" <[email hidden]> wrote in message news:[email hidden]...
Quoted text (17 lines)> > I've always said Papy (& their heirs, assigns & successors) could make a > > fortune licensing: > > > > 1. Their physics engine. > > Not these days... > > > 2. Their controller algorithms. > > ..which are non-standard and are basically the main cause of the current > mess. > > > 3. Their replay routine & UI. > > yes, definitely. > >
> The N2003 physics engine still beats anything out there, IMO (altho GTR's > is > getting closer and closer). RBR beats it in all departments (except maybe aero) GTR beats it in some departments (the ones that matter for mine) > There are no controller standards. Papy's calibration routines have > always > been bulletproof. Er...DirectInput? Windows joystick control panel calibration? (designed so that you shouldn't need to calibrate your controller in every game) > I forgot 4. Their multiplayer code. Still the best, IMO. Totally irrelevant but yes, I agree.
Hey, these high end wheels work with the Papy games, EA games, as well as Codemasters games so its not the wheel. Its the off brand games such as Rally Trophy from Bugbear<sp?> and now RBR, developed by Warthog???, that is the problem because of their narrow controller support. Quit fussing about Papy and these controllers and get a clue ... "Steve Simpson" <[email hidden]> wrote in message news:[email hidden]...
Quoted text (9 lines)>> IF you have any non-standard controller setup, that is. >> >> My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is >> recognized, but the damn brake is reversed and nothing I try seems to >> fix it. >> >> For a sim targeted at high-end users, they better cobble a patch >> together. Sounds like a lot of people w TSW/ECCI gear have the same >> problem.
> Er...DirectInput? Windows joystick control panel calibration? (designedso > that you shouldn't need to calibrate your controller in every game) Agree - Games should not need to include their own Calibration routines - this should be handled by the Game Controller's Control Panel implementation. Microsoft do state that only Control Panel type applications should request or manipulate raw joystick inputs ie. in the DirectX DirectInput API doco. To be fair to Papy, this doco was probably not available or unclear back in the DirectX 4/5 days when GPL was written. To Papy's credit they did provide support for both DirectInput and Direct Gameport access in their games. "Steve Simpson" <[email hidden]> wrote in message news:[email hidden]... > > The N2003 physics engine still beats anything out there, IMO (althoGTR's
Quoted text (11 lines)> > is > > getting closer and closer). > > RBR beats it in all departments (except maybe aero) GTR beats it in some > departments (the ones that matter for mine) > > > There are no controller standards. Papy's calibration routines have > > always > > been bulletproof. > > Er...DirectInput? Windows joystick control panel calibration? (designed
so
Quoted text (7 lines)> that you shouldn't need to calibrate your controller in every game) > > > I forgot 4. Their multiplayer code. Still the best, IMO. > > Totally irrelevant but yes, I agree. > >
My ECCI works fine with a little tuning. Can't tell you what I did, just moved pot wires around til it worked. You do have to reset the controller in the game when you change wires around. "Kendt Eklund" <[email hidden]> wrote in message news:[email hidden]...
Quoted text (11 lines)> IF you have any non-standard controller setup, that is. > > My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is > recognized, but the damn brake is reversed and nothing I try seems to > fix it. > > For a sim targeted at high-end users, they better cobble a patch > together. Sounds like a lot of people w TSW/ECCI gear have the same > problem. > > Kendt
Lets not forget their multiplayer capabilities! "Steve Smith" <[email hidden]> wrote in message news:KUA2d.72691$[email hidden]...
Quoted text (35 lines)> I've always said Papy (& their heirs, assigns & successors) could make a > fortune licensing: > > 1. Their physics engine. > 2. Their controller algorithms. > 3. Their replay routine & UI. > > But noooooooooooooooooo............ > > "Steve Simpson" <[email hidden]> wrote in message > news:[email hidden]... >> > IF you have any non-standard controller setup, that is. >> > >> > My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is >> > recognized, but the damn brake is reversed and nothing I try seems to >> > fix it. >> > >> > For a sim targeted at high-end users, they better cobble a patch >> > together. Sounds like a lot of people w TSW/ECCI gear have the same >> > problem. >> >> What's the deal with all these so-called high-end controllers? Do they > not >> have proper Direct X driver support for split axis pedals? The only >> games >> they seem to support are Papyrus games which use a proprietry controller >> routine. It's the same old story with every game release. Game > developers >> have to fudge their controller routines just so that they work with the >> outdated drivers for these things. Sorry if I sound like I'm moaning but >> I'm getting really sick of this every time a game is released. :-\ >> >> > >
Direct Input is not really that good. Dual-axis has always been fudgy in Windows and most games you buy will see dual axis pedals and will think you are pressing up or down. Theres no standard for axes at all and even non-driving games have tons of issues with gamepads and anything that isnt a vanilla joystick.
On Fri, 17 Sep 2004 22:33:07 +1000, Steve Simpson wrote: > What's the deal with all these so-called high-end controllers? Do they not > have proper Direct X driver support for split axis pedals? Fact: Papy games have worked with my TSW since GPL (and probably earlier, but I used a Thrustmaster F1 in those days) Fact: No other sim that relies purely on the DirectX routines (RT, CMx, F1 200x) has worked with the DirectX routines out of the box. Even in F1C I needed to copy over some tweaked player profile from F1 2002 in order to get it to work. GT Racing demo works, so does LFS, so did Racer and netkar last I tried. Ergo: DirectInput sucks dead bunnies through a garden hose. Might have changed with 9.0x, but who am I to judge, not doing any windows based programming. > outdated drivers for these things. Sorry if I sound like I'm moaning but > I'm getting really sick of this every time a game is released. :-\ Why should a gameport device need its own drivers? Those ports have been standardized since when, 1980? ;-) Developers simply should take a bit more care, that's all. Cheers, uwe -- mail replies to Uwe at schuerkamp dot de ( yahoo address is spambox) Uwe Schuerkamp //////////////////////////// http://www.schuerkamp.de/ Herford, Germany \\\\\\\\\\\\\\\\\\\\\\\\\\ (52.0N/8.5E) GPG Fingerprint: 2E 13 20 22 9A 3F 63 7F 67 6F E9 B1 A8 36 A4 61
Kendt Eklund 17 Sep 2004 20:33 UTC↳ reply to AD#31845
"AD" <[email hidden]> wrote in message news:<ciel0e$3vn$[email hidden]>... > I had the same with my Act Labs but cured it with DXTweak 2 by just clicking > the brake axis and then Axis Defaults then apply then started the game and > went into controllers and assigned as normal..it took a bit of working out > but as along as no other axis were touched in DXT2 it was perfect. > > AD Thanks! I'll give it a shot. How'd you find the FF for your Act-Labs? All I've done so far is turn off the wheel centering in the FF setup. I've got everything in the control panel settings at 100%. One thing I haven't done is adjust the steering response curves from the defaults. Do you run full linear? Come on devs - this isn't rocket science! My controller reports a full range of motion, I just need to reverse the damn thing! Kendt
BRH 18 Sep 2004 02:27 UTC↳ reply to AD#31865
I tried that procedure with my TSW peds. However, after clicking Axis default for my brake axis (In my case, it's Y), there was very little range of motion indicated in DXTweak2. Nevertheless, I went ahead and clicked on Apply and started RBR. Although I was able to set the brake to the Y axis on the controller screen, the bar was always fully applied (full red) no matter what I was doing with the brake. Any idea on what might be wrong? I'll admit that I don't fully understand how to use DXTweak. Perhaps I missed a step that would be obvious to others. Thanks! AD wrote:
Quoted text (19 lines)> I had the same with my Act Labs but cured it with DXTweak 2 by just clicking > the brake axis and then Axis Defaults then apply then started the game and > went into controllers and assigned as normal..it took a bit of working out > but as along as no other axis were touched in DXT2 it was perfect. > > AD > "Kendt Eklund" <[email hidden]> wrote in message > news:[email hidden]... > > IF you have any non-standard controller setup, that is. > > > > My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is > > recognized, but the damn brake is reversed and nothing I try seems to > > fix it. > > > > For a sim targeted at high-end users, they better cobble a patch > > together. Sounds like a lot of people w TSW/ECCI gear have the same > > problem. > > > > Kendt
bhoeni 18 Sep 2004 02:27 UTC#531985
I tried that procedure with my TSW peds. However, after clicking Axis default for my brake axis (In my case, it's Y), there was very little range of motion indicated in DXTweak2. Nevertheless, I went ahead and clicked on Apply and started RBR. Although I was able to set the brake to the Y axis on the controller screen, the bar was always fully applied (full red) no matter what I was doing with the brake. Any idea on what might be wrong? I'll admit that I don't fully understand how to use DXTweak. Perhaps I missed a step that would be obvious to others. Thanks!
Quoted text (19 lines)> I had the same with my Act Labs but cured it with DXTweak 2 by just clicking > the brake axis and then Axis Defaults then apply then started the game and > went into controllers and assigned as normal..it took a bit of working out > but as along as no other axis were touched in DXT2 it was perfect. > AD > > IF you have any non-standard controller setup, that is. > > My Act-Labs wheel/Thrustmaster pedal combo (2 separate controllers) is > > recognized, but the damn brake is reversed and nothing I try seems to > > fix it. > > For a sim targeted at high-end users, they better cobble a patch > > together. Sounds like a lot of people w TSW/ECCI gear have the same > > problem. > > Kendt
"Steve Simpson" <[email hidden]> wrote in news:2r05qtF1342f9U1@uni- berlin.de:
Quoted text (11 lines)>> I've always said Papy (& their heirs, assigns & successors) could make a >> fortune licensing: >> >> 1. Their physics engine. > > Not these days... > >> 2. Their controller algorithms. > > ..which are non-standard and are basically the main cause of the current > mess.
Cause of the current mess is poor DirectInput implementation. So developers either use DirectX and have problems like RBR does or write their own routines (like Papy). Alex.
"Uwe Sch�rkamp" wrote... > <snip> > Why should a gameport device need its own drivers? Those ports > have been standardized since when, 1980? ;-) Developers simply > should take a bit more care, that's all. Problem 1: gameports used to be standardised NE555 monostable multivibrators where the joystick pot was the timing element, but they were too slow to really work with our modern day, high update rate simulations, so now pots are sampled by A/D conversion and scaled to provide the correct values for DirectX. As far as I know this "layer" of the API is manufacturer specific. Problem 2: Windows XP's achitecture doesn't allow applications to talk to hardware directly (for damn good reasons, IMO). So games end up using the codemonkeys' interpretation of the API, which may or may not be exactly right or compatible with all gameports/devices (assuming those were constructed/written correctly to support DirectX in the first place). But I agree, if some developers can get it right, their competition should get it right too. I was impressed by the ISI/SimBin guys recently. I wanted to show GPL and GTR to a friend, only to find the pedals on my MOMO were dead (connection to the wheel broken). So I broke out my trusty LWFF. So far so good, but the pedals are wired differently, so I had to recalibrate. I got annoyed when I noticed the pedals were both reported as combined (Y) and individually (RX and RY) by the drivers and GPL would only select the combined axis for gas and brake. GTR, however, didn't miss a beat and recognised the wheel in split axis mode. Good stuff. I've since repaired the MOMO and consigned the LWFF to the rubbish bin (rubber covering wheel had gone tacky and the movement had all but seezed up through non-use). Jan. =---
BRH....DXTweak will make any axis do what you require it to and not what it is supposed actually wants to do.....i have used it many time to do various things but i have never needed to reverse/invert an axis so i dont know if it will/can do that..i am sure it probably can...might be worth going to the Wingman webpage where DXTweak2 is from and reading whats there...they might even have a forum... AD "Jan Verschueren" <[email hidden]> wrote in message news:7mT2d.249719$[email hidden]...
Quoted text (7 lines)> "Uwe Sch�rkamp" wrote... > > <snip> > > Why should a gameport device need its own drivers? Those ports > > have been standardized since when, 1980? ;-) Developers simply > > should take a bit more care, that's all. > > Problem 1: gameports used to be standardised NE555 monostable
multivibrators > where the joystick pot was the timing element, but they were too slow to > really work with our modern day, high update rate simulations, so now pots > are sampled by A/D conversion and scaled to provide the correct values for > DirectX. As far as I know this "layer" of the API is manufacturerspecific. > > Problem 2: Windows XP's achitecture doesn't allow applications to talk to > hardware directly (for damn good reasons, IMO). > > So games end up using the codemonkeys' interpretation of the API, whichmay > or may not be exactly right or compatible with all gameports/devices > (assuming those were constructed/written correctly to support DirectX inthe
Quoted text (7 lines)> first place). > > But I agree, if some developers can get it right, their competition should > get it right too. > > I was impressed by the ISI/SimBin guys recently. I wanted to show GPL and > GTR to a friend, only to find the pedals on my MOMO were dead (connection
to > the wheel broken). So I broke out my trusty LWFF. So far so good, but the > pedals are wired differently, so I had to recalibrate. I got annoyed whenI
Quoted text (7 lines)> noticed the pedals were both reported as combined (Y) and individually (RX > and RY) by the drivers and GPL would only select the combined axis for gas > and brake. GTR, however, didn't miss a beat and recognised the wheel in > split axis mode. Good stuff. > > I've since repaired the MOMO and consigned the LWFF to the rubbish bin > (rubber covering wheel had gone tacky and the movement had all but seezed
up > through non-use). > > Jan. > =--- > >
BRH 18 Sep 2004 12:38 UTC↳ reply to AD#31884
Thanks AD. I played a bit more with DXTweak2 and got full range on the brakes, but they still are reversed. 8( Unfortunately, I also did something which resulted in the throttle not being recognized (within game) anymore. -- Double 8(. Oh well, I guess that I'll just have to use my Logi peds with this sim until a patch comes out that fixes this. Thanks! AD wrote:
Quoted text (57 lines)> BRH....DXTweak will make any axis do what you require it to and not what it > is supposed actually wants to do.....i have used it many time to do various > things but i have never needed to reverse/invert an axis so i dont know if > it will/can do that..i am sure it probably can...might be worth going to the > Wingman webpage where DXTweak2 is from and reading whats there...they might > even have a forum... > > AD > "Jan Verschueren" <[email hidden]> wrote in message > news:7mT2d.249719$[email hidden]... > > "Uwe Sch�rkamp" wrote... > > > <snip> > > > Why should a gameport device need its own drivers? Those ports > > > have been standardized since when, 1980? ;-) Developers simply > > > should take a bit more care, that's all. > > > > Problem 1: gameports used to be standardised NE555 monostable > multivibrators > > where the joystick pot was the timing element, but they were too slow to > > really work with our modern day, high update rate simulations, so now pots > > are sampled by A/D conversion and scaled to provide the correct values for > > DirectX. As far as I know this "layer" of the API is manufacturer > specific. > > > > Problem 2: Windows XP's achitecture doesn't allow applications to talk to > > hardware directly (for damn good reasons, IMO). > > > > So games end up using the codemonkeys' interpretation of the API, which > may > > or may not be exactly right or compatible with all gameports/devices > > (assuming those were constructed/written correctly to support DirectX in > the > > first place). > > > > But I agree, if some developers can get it right, their competition should > > get it right too. > > > > I was impressed by the ISI/SimBin guys recently. I wanted to show GPL and > > GTR to a friend, only to find the pedals on my MOMO were dead (connection > to > > the wheel broken). So I broke out my trusty LWFF. So far so good, but the > > pedals are wired differently, so I had to recalibrate. I got annoyed when > I > > noticed the pedals were both reported as combined (Y) and individually (RX > > and RY) by the drivers and GPL would only select the combined axis for gas > > and brake. GTR, however, didn't miss a beat and recognised the wheel in > > split axis mode. Good stuff. > > > > I've since repaired the MOMO and consigned the LWFF to the rubbish bin > > (rubber covering wheel had gone tacky and the movement had all but seezed > up > > through non-use). > > > > Jan. > > =--- > > > >
bhoeni 18 Sep 2004 12:38 UTC#531989
Thanks AD. I played a bit more with DXTweak2 and got full range on the brakes, but they still are reversed. 8( Unfortunately, I also did something which resulted in the throttle not being recognized (within game) anymore. -- Double 8(. Oh well, I guess that I'll just have to use my Logi peds with this sim until a patch comes out that fixes this. Thanks!
Quoted text (55 lines)> BRH....DXTweak will make any axis do what you require it to and not what it > is supposed actually wants to do.....i have used it many time to do various > things but i have never needed to reverse/invert an axis so i dont know if > it will/can do that..i am sure it probably can...might be worth going to the > Wingman webpage where DXTweak2 is from and reading whats there...they might > even have a forum... > AD > > "Uwe Schrkamp" wrote... > > > <snip> > > > Why should a gameport device need its own drivers? Those ports > > > have been standardized since when, 1980? ;-) Developers simply > > > should take a bit more care, that's all. > > Problem 1: gameports used to be standardised NE555 monostable > multi***s > > where the joystick pot was the timing element, but they were too slow to > > really work with our modern day, high update rate simulations, so now pots > > are sampled by A/D conversion and scaled to provide the correct values for > > DirectX. As far as I know this "layer" of the API is manufacturer > specific. > > Problem 2: Windows XP's achitecture doesn't allow applications to talk to > > hardware directly (for damn good reasons, IMO). > > So games end up using the codemonkeys' interpretation of the API, which > may > > or may not be exactly right or compatible with all gameports/devices > > (assuming those were constructed/written correctly to support DirectX in > the > > first place). > > But I agree, if some developers can get it right, their competition should > > get it right too. > > I was impressed by the ISI/SimBin guys recently. I wanted to show GPL and > > GTR to a friend, only to find the pedals on my MOMO were dead (connection > to > > the wheel broken). So I broke out my trusty LWFF. So far so good, but the > > pedals are wired differently, so I had to recalibrate. I got annoyed when > I > > noticed the pedals were both reported as combined (Y) and individually (RX > > and RY) by the drivers and GPL would only select the combined axis for gas > > and brake. GTR, however, didn't miss a beat and recognised the wheel in > > split axis mode. Good stuff. > > I've since repaired the MOMO and consigned the LWFF to the rubbish bin > > (*** covering wheel had gone tacky and the movement had all but seezed > up > > through non-use). > > Jan. > > =---
AD 18 Sep 2004 13:14 UTC↳ reply to BRH#31886
BRH i have played about with DXT2 on your behalf and found out what you have to do... Just manually swap the linear Y axis it is so easy i dont know why i didnt think of it before... At the moment when you click the Y axis you see 3 figures at the top under Calibration...mine read as :- Min 22 Cen 128 Max 254 If i change them to :- Min 254 Cen 128 Max 22 i have reversed action...LOL Simple :) have fun mate AD "BRH @comcast.net>" <"bhoenig<no-spam> wrote in message news:[email hidden]... > Thanks AD. I played a bit more with DXTweak2 and got full range on thebrakes, > but they still are reversed. 8( Unfortunately, I also did somethingwhich > resulted in the throttle not being recognized (within game) anymore. -- Double > 8(. > > Oh well, I guess that I'll just have to use my Logi peds with this simuntil a
Quoted text (7 lines)> patch comes out that fixes this. > > Thanks! > > AD wrote: > > > BRH....DXTweak will make any axis do what you require it to and not what
it > > is supposed actually wants to do.....i have used it many time to dovarious > > things but i have never needed to reverse/invert an axis so i dont knowif > > it will/can do that..i am sure it probably can...might be worth going tothe > > Wingman webpage where DXTweak2 is from and reading whats there...theymight
Quoted text (14 lines)> > even have a forum... > > > > AD > > "Jan Verschueren" <[email hidden]> wrote in message > > news:7mT2d.249719$[email hidden]... > > > "Uwe Sch�rkamp" wrote... > > > > <snip> > > > > Why should a gameport device need its own drivers? Those ports > > > > have been standardized since when, 1980? ;-) Developers simply > > > > should take a bit more care, that's all. > > > > > > Problem 1: gameports used to be standardised NE555 monostable > > multivibrators > > > where the joystick pot was the timing element, but they were too slow
to > > > really work with our modern day, high update rate simulations, so nowpots > > > are sampled by A/D conversion and scaled to provide the correct valuesfor > > > DirectX. As far as I know this "layer" of the API is manufacturer > > specific. > > > > > > Problem 2: Windows XP's achitecture doesn't allow applications to talkto > > > hardware directly (for damn good reasons, IMO). > > > > > > So games end up using the codemonkeys' interpretation of the API,which > > may > > > or may not be exactly right or compatible with all gameports/devices > > > (assuming those were constructed/written correctly to support DirectXin > > the > > > first place). > > > > > > But I agree, if some developers can get it right, their competitionshould > > > get it right too. > > > > > > I was impressed by the ISI/SimBin guys recently. I wanted to show GPLand > > > GTR to a friend, only to find the pedals on my MOMO were dead(connection > > to > > > the wheel broken). So I broke out my trusty LWFF. So far so good, butthe > > > pedals are wired differently, so I had to recalibrate. I got annoyedwhen > > I > > > noticed the pedals were both reported as combined (Y) and individually(RX > > > and RY) by the drivers and GPL would only select the combined axis forgas > > > and brake. GTR, however, didn't miss a beat and recognised the wheelin > > > split axis mode. Good stuff. > > > > > > I've since repaired the MOMO and consigned the LWFF to the rubbish bin > > > (rubber covering wheel had gone tacky and the movement had all butseezed
Quoted text (8 lines)> > up > > > through non-use). > > > > > > Jan. > > > =--- > > > > > > >
>"Steve Simpson" <[email hidden]> wrote > RBR beats it "beats it". Such a subjective way to write. It'll take much more than just that. -- -- Fran�ois M�nard <ymenard> -- This announcement is brought to you by the Shimago-Dominguez Corporation - helping America into the New World...
BRH 18 Sep 2004 19:45 UTC↳ reply to AD#31803
I tried that, AD. However, DXT2 doesn't allow my minimum to be a larger value than my maximum! How did you manage to get DXT2 to allow this? Maybe you have an updated version? The one I'm using came from www.wingmanteam.com and the version shown at the top is 4.30.229. AD wrote:
Quoted text (116 lines)> BRH i have played about with DXT2 on your behalf and found out what you have > to do... > > Just manually swap the linear Y axis it is so easy i dont know why i didnt > think of it before... > > At the moment when you click the Y axis you see 3 figures at the top under > Calibration...mine read as :- > > Min 22 Cen 128 Max 254 > > If i change them to :- > > Min 254 Cen 128 Max 22 > > i have reversed action...LOL > > Simple :) have fun mate > > AD > "BRH @comcast.net>" <"bhoenig<no-spam> wrote in message > news:[email hidden]... > > Thanks AD. I played a bit more with DXTweak2 and got full range on the > brakes, > > but they still are reversed. 8( Unfortunately, I also did something > which > > resulted in the throttle not being recognized (within game) anymore. -- > Double > > 8(. > > > > Oh well, I guess that I'll just have to use my Logi peds with this sim > until a > > patch comes out that fixes this. > > > > Thanks! > > > > AD wrote: > > > > > BRH....DXTweak will make any axis do what you require it to and not what > it > > > is supposed actually wants to do.....i have used it many time to do > various > > > things but i have never needed to reverse/invert an axis so i dont know > if > > > it will/can do that..i am sure it probably can...might be worth going to > the > > > Wingman webpage where DXTweak2 is from and reading whats there...they > might > > > even have a forum... > > > > > > AD > > > "Jan Verschueren" <[email hidden]> wrote in message > > > news:7mT2d.249719$[email hidden]... > > > > "Uwe Sch�rkamp" wrote... > > > > > <snip> > > > > > Why should a gameport device need its own drivers? Those ports > > > > > have been standardized since when, 1980? ;-) Developers simply > > > > > should take a bit more care, that's all. > > > > > > > > Problem 1: gameports used to be standardised NE555 monostable > > > multivibrators > > > > where the joystick pot was the timing element, but they were too slow > to > > > > really work with our modern day, high update rate simulations, so now > pots > > > > are sampled by A/D conversion and scaled to provide the correct values > for > > > > DirectX. As far as I know this "layer" of the API is manufacturer > > > specific. > > > > > > > > Problem 2: Windows XP's achitecture doesn't allow applications to talk > to > > > > hardware directly (for damn good reasons, IMO). > > > > > > > > So games end up using the codemonkeys' interpretation of the API, > which > > > may > > > > or may not be exactly right or compatible with all gameports/devices > > > > (assuming those were constructed/written correctly to support DirectX > in > > > the > > > > first place). > > > > > > > > But I agree, if some developers can get it right, their competition > should > > > > get it right too. > > > > > > > > I was impressed by the ISI/SimBin guys recently. I wanted to show GPL > and > > > > GTR to a friend, only to find the pedals on my MOMO were dead > (connection > > > to > > > > the wheel broken). So I broke out my trusty LWFF. So far so good, but > the > > > > pedals are wired differently, so I had to recalibrate. I got annoyed > when > > > I > > > > noticed the pedals were both reported as combined (Y) and individually > (RX > > > > and RY) by the drivers and GPL would only select the combined axis for > gas > > > > and brake. GTR, however, didn't miss a beat and recognised the wheel > in > > > > split axis mode. Good stuff. > > > > > > > > I've since repaired the MOMO and consigned the LWFF to the rubbish bin > > > > (rubber covering wheel had gone tacky and the movement had all but > seezed > > > up > > > > through non-use). > > > > > > > > Jan. > > > > =--- > > > > > > > > > >
bhoeni 18 Sep 2004 19:45 UTC#531990
I tried that, AD. However, DXT2 doesn't allow my minimum to be a larger value than my maximum! How did you manage to get DXT2 to allow this? Maybe you have an updated version? The one I'm using came from www.wingmanteam.com and the version shown at the top is 4.30.229.
Quoted text (114 lines)> BRH i have played about with DXT2 on your behalf and found out what you have > to do... > Just manually swap the linear Y axis it is so easy i dont know why i didnt > think of it before... > At the moment when you click the Y axis you see 3 figures at the top under > Calibration...mine read as :- > Min 22 Cen 128 Max 254 > If i change them to :- > Min 254 Cen 128 Max 22 > i have reversed action...LOL > Simple :) have fun mate > AD > > Thanks AD. I played a bit more with DXTweak2 and got full range on the > brakes, > > but they still are reversed. 8( Unfortunately, I also did something > which > > resulted in the throttle not being recognized (within game) anymore. -- > Double > > 8(. > > Oh well, I guess that I'll just have to use my Logi peds with this sim > until a > > patch comes out that fixes this. > > Thanks! > > > BRH....DXTweak will make any axis do what you require it to and not what > it > > > is supposed actually wants to do.....i have used it many time to do > various > > > things but i have never needed to reverse/invert an axis so i dont know > if > > > it will/can do that..i am sure it probably can...might be worth going to > the > > > Wingman webpage where DXTweak2 is from and reading whats there...they > might > > > even have a forum... > > > AD > > > > "Uwe Schrkamp" wrote... > > > > > <snip> > > > > > Why should a gameport device need its own drivers? Those ports > > > > > have been standardized since when, 1980? ;-) Developers simply > > > > > should take a bit more care, that's all. > > > > Problem 1: gameports used to be standardised NE555 monostable > > > multi***s > > > > where the joystick pot was the timing element, but they were too slow > to > > > > really work with our modern day, high update rate simulations, so now > pots > > > > are sampled by A/D conversion and scaled to provide the correct values > for > > > > DirectX. As far as I know this "layer" of the API is manufacturer > > > specific. > > > > Problem 2: Windows XP's achitecture doesn't allow applications to talk > to > > > > hardware directly (for damn good reasons, IMO). > > > > So games end up using the codemonkeys' interpretation of the API, > which > > > may > > > > or may not be exactly right or compatible with all gameports/devices > > > > (assuming those were constructed/written correctly to support DirectX > in > > > the > > > > first place). > > > > But I agree, if some developers can get it right, their competition > should > > > > get it right too. > > > > I was impressed by the ISI/SimBin guys recently. I wanted to show GPL > and > > > > GTR to a friend, only to find the pedals on my MOMO were dead > (connection > > > to > > > > the wheel broken). So I broke out my trusty LWFF. So far so good, but > the > > > > pedals are wired differently, so I had to recalibrate. I got annoyed > when > > > I > > > > noticed the pedals were both reported as combined (Y) and individually > (RX > > > > and RY) by the drivers and GPL would only select the combined axis for > gas > > > > and brake. GTR, however, didn't miss a beat and recognised the wheel > in > > > > split axis mode. Good stuff. > > > > I've since repaired the MOMO and consigned the LWFF to the rubbish bin > > > > (*** covering wheel had gone tacky and the movement had all but > seezed > > > up > > > > through non-use). > > > > Jan. > > > > =---
Kendt Eklund 19 Sep 2004 00:11 UTC↳ reply to AD#31824
"AD" <[email hidden]> wrote in message news:<cihcaj$efe$[email hidden]>... > BRH i have played about with DXT2 on your behalf and found out what you have > to do... What version of DXT2 are you running? I had tried this with the 4.20 beta, and it wouldn't work (it wouldn't accept a Min value higher than the Max), and I downloaded the latest 4.30 version and it does the same thing. TIA, Kendt
>"Steve Simpson" <[email hidden]> wrote >> "beats it". Such a subjective way to write. It'll take much more >> than just that. > > Play it. You'll see... Like I haven't. To say a sim "beats it" is purely subjective. That's all. I find certain aspects, in majority, of NR2003 to be superior to any sim at this date, still. Now that doesn't mean other sims have a better "r�pertoire" of certain aspects that makes them great sims. -- -- Fran�ois M�nard <ymenard> -- This announcement is brought to you by the Shimago-Dominguez Corporation - helping America into the New World...
> Like I haven't. To say a sim "beats it" is purely subjective. That's > all. I find certain aspects, in majority, of NR2003 to be superior to any > sim at this date, still. Now that doesn't mean other sims have a better > "r�pertoire" of certain aspects that makes them great sims. <yawn> not interested in semantics...
>"Steve Simpson" <[email hidden]> wrote > <yawn> not interested in semantics... Look man "you" started it first with the "XYZ beats ZYX" thingy. It's, again, completely subjective. To simply say "beats it" at various points in a reply, leads to nothing. Why not develop and expand on this and be more comprehensive of the situation that is the Usenet and the power you have to really set up your point intelligently. -- -- Fran�ois M�nard <ymenard> -- This announcement is brought to you by the Shimago-Dominguez Corporation - helping America into the New World...
Pete 19 Sep 2004 09:05 UTC↳ reply to ymenard#31834
Frank, go get the game and try it. Pete "ymenard" <[email hidden]> wrote in message news:i_a3d.1016$[email hidden]... > >"Steve Simpson" <[email hidden]> wrote > > > Look man "you" started it first with the "XYZ beats ZYX" thingy. It's, > again, completely subjective. To simply say "beats it" at various pointsin > a reply, leads to nothing. Why not develop and expand on this and be more > comprehensive of the situation that is the Usenet and the power you haveto
Quoted text (11 lines)> really set up your point intelligently. > > > > > -- > -- Frangois Minard <ymenard> > -- This announcement is brought to you by the Shimago-Dominguez > Corporation - helping America into the New World... > >
ymenard 19 Sep 2004 17:37 UTC↳ reply to Pete#31707
>"Pete" <[email hidden]> wrote > Frank, go get the game and try it. Read the thread you'll see that I have it. -- -- Fran�ois M�nard <ymenard> -- This announcement is brought to you by the Shimago-Dominguez Corporation - helping America into the New World...
Pete 19 Sep 2004 20:45 UTC↳ reply to ymenard#31714
It was late missed that part. Pete "ymenard" <[email hidden]> wrote in message news:ktj3d.4263$[email hidden]...
Quoted text (15 lines)> >"Pete" <[email hidden]> wrote > Read the thread you'll see that I have it. > > > > > > > -- > -- Frangois Minard <ymenard> > -- This announcement is brought to you by the Shimago-Dominguez > Corporation - helping America into the New World... > >

Sponsors

Affiliate Links

Sim Gaming Expo MOZA Racing Sim-Lab Fanatec TrakRacer Asetek Internet Privacy From NordVPN Dreamhost Capital One Credit Card Application Fanatical CDKeys Amazon Amazon UK Project Motor Racing iRacing Get your racing gloves, boots and more from Demon Tweeks. Enlist at Roberts Space Industries, developers of Star Citizen and Squadron 42


Back from the ashes since July, 2019. First created in 2001 with the merger of Legends Central (founded 1999) and simracing.dk.

A site by a sort of sim racer, for sim racers, about racing sims. News and information on both modern and historic sim racing software titles.

All products and licenses property of their respective owners.


Facebook Threads Bluesky Twitter Mastodon Instagram YouTube Tiktok Twitch Reddit Google News Apple News Subscribe via WordPress Flipboard eBay

Race Sim Central © 1999-2026 | Some links pay RSC a commission. Advertising does not equal endorsement.Cookie Policy