I could probably go on forever with this topic.

Ramones - Blitzkrieg Bop

Minor Threat - Salad Days

Last edited by bdshan, Mon, 9 Aug 2010 19:03.

For information on the formation of the next LOTA series, please refer to: http://www.lfs-lota.net/index.php?topic=1965.0

I interpreted it a bit differently.

Quote :

We will offer this kit as a stand alone kit for 40 EURO / USD. This is our cost price and we consider this offer as service.


If you are not a big DYI fan you can also send us the wheel and we will make the transformation for you. We have service agents in Germany and California.


The price of the service is 30 EUR / USD plus shipping costs in both ways.

$40 for parts + $30 for service + shipping both ways.

Quote from NightShift :

I wonder why they don't just handle the cars normally when in the pits. If drivers will try their best to avoid accidents on the track, why not in the pit lane/stalls?

It is a simulation after all!

Did you change the degrees of rotation in LFS? Set LFS and the wheel to 720.

I always filled out the web form. That starts the RMA ball rolling. Did you email Armin as I suggested? He has always been super responsive with me.

Did you just email support or did you fill out this web form, http://www.fanatec.de/webshop/ ... 74d320e2783a44ff7621ad4fb?

Rusty Screw Nomination: Elderchop29; Heat #2 LFS said he did not finish when in fact he finished in front of me.

PayPal is my preferred method of payment for all online transactions. Yes, safe and easy.

You know I have read about that issue before, but I can't say that any of my wheels had any perceptible play in the shaft. Maybe the first one a little. I never used the second wheel. My current wheel has no play at all.

Are you listening for the button click event? If not, do so. Then compare the button id to something and take the appropriate action.

From the insim text file.

Quote :

// BUTTONS
// =======

// You can make up to 240 buttons appear on the host or guests (ID = 0 to 239).
// You should set the ISF_LOCAL flag (in IS_ISI) if your program is not a host control
// system, to make sure your buttons do not conflict with any buttons sent by the host.

// LFS can display normal buttons in these four screens :

// - main entry screen
// - game setup screen
// - in game
// - SHIFT+U mode

// The recommended area for most buttons is defined by :

#define IS_X_MIN 0
#define IS_X_MAX 110

#define IS_Y_MIN 30
#define IS_Y_MAX 170

// If you draw buttons in this area, the area will be kept clear to
// avoid overlapping LFS buttons with your InSim program's buttons.
// Buttons outside that area will not have a space kept clear.
// You can also make buttons visible in all screens - see below.

// To delete one button or clear all buttons, send this packet :

struct IS_BFN // Button FunctioN - delete buttons / receive button requests
{
byte Size; // 8
byte Type; // ISP_BFN
byte ReqI; // 0
byte SubT; // subtype, from BFN_ enumeration (see below)

byte UCID; // connection to send to or from (0 = local / 255 = all)
byte ClickID; // ID of button to delete (if SubT is BFN_DEL_BTN)
byte Inst; // used internally by InSim
byte Sp3;
};

enum // the fourth byte of IS_BFN packets is one of these
{
BFN_DEL_BTN, // 0 - instruction : delete one button (must set ClickID)
BFN_CLEAR, // 1 - instruction : clear all buttons made by this insim instance
BFN_USER_CLEAR, // 2 - info : user cleared this insim instance's buttons
BFN_REQUEST, // 3 - user request : SHIFT+B or SHIFT+I - request for buttons
};

// NOTE : BFN_REQUEST allows the user to bring up buttons with SHIFT+B or SHIFT+I

// SHIFT+I clears all host buttons if any - or sends a BFN_REQUEST to host instances
// SHIFT+B is the same but for local buttons and local instances

// To send a button to LFS, send this variable sized packet

struct IS_BTN // BuTtoN - button header - followed by 0 to 240 characters
{
byte Size; // 12 + TEXT_SIZE (a multiple of 4)
byte Type; // ISP_BTN
byte ReqI; // non-zero (returned in IS_BTC and IS_BTT packets)
byte UCID; // connection to display the button (0 = local / 255 = all)

byte ClickID; // button ID (0 to 239)
byte Inst; // some extra flags - see below
byte BStyle; // button style flags - see below
byte TypeIn; // max chars to type in - see below

byte L; // left : 0 - 200
byte T; // top : 0 - 200
byte W; // width : 0 - 200
byte H; // height : 0 - 200

// char Text[TEXT_SIZE]; // 0 to 240 characters of text
};

// ClickID byte : this value is returned in IS_BTC and IS_BTT packets.

// Host buttons and local buttons are stored separately, so there is no chance of a conflict between
// a host control system and a local system (although the buttons could overlap on screen).

// Programmers of local InSim programs may wish to consider using a configurable button range and
// possibly screen position, in case their users will use more than one local InSim program at once.

// TypeIn byte : if set, the user can click this button to type in text.

// Lowest 7 bits are the maximum number of characters to type in (0 to 95)
// Highest bit (128) can be set to initialise dialog with the button's text

// On clicking the button, a text entry dialog will be opened, allowing the specified number of
// characters to be typed in. The caption on the text entry dialog is optionally customisable using
// Text in the IS_BTN packet. If the first character of IS_BTN's Text field is zero, LFS will read
// the caption up to the second zero. The visible button text then follows that second zero.

// Text : 0-65-66-0 would display button text "AB" and no caption

// Text : 0-65-66-67-0-68-69-70-71-0-0-0 would display button text "DEFG" and caption "ABC"

// Inst byte : mainly used internally by InSim but also provides some extra user flags

#define INST_ALWAYS_ON 128 // if this bit is set the button is visible in all screens

// NOTE : You should not use INST_ALWAYS_ON for most buttons. This is a special flag for buttons
// that really must be on in all screens (including the garage and options screens). You will
// probably need to confine these buttons to the top or bottom edge of the screen, to avoid
// overwriting LFS buttons. Most buttons should be defined without this flag, and positioned
// in the recommended area so LFS can keep a space clear in the main screens.

// BStyle byte : style flags for the button

#define ISB_C1 1 // you can choose a standard
#define ISB_C2 2 // interface colour using
#define ISB_C4 4 // these 3 lowest bits - see below
#define ISB_CLICK 8 // click this button to send IS_BTC
#define ISB_LIGHT 16 // light button
#define ISB_DARK 32 // dark button
#define ISB_LEFT 64 // align text to left
#define ISB_RIGHT 128 // align text to right

// colour 0 : light grey (not user editable)
// colour 1 : title colour (default:yellow)
// colour 2 : unselected text (default:black)
// colour 3 : selected text (default:white)
// colour 4 : ok (default:green)
// colour 5 : cancel (default:red)
// colour 6 : text string (defaultale blue)
// colour 7 : unavailable (default:grey)

// NOTE : If width or height are zero, this would normally be an invalid button. But in that case if
// there is an existing button with the same ClickID, all the packet contents are ignored except the
// Text field. This can be useful for updating the text in a button without knowing its position.
// For example, you might reply to an IS_BTT using an IS_BTN with zero W and H to update the text.

// Replies : If the user clicks on a clickable button, this packet will be sent :

struct IS_BTC // BuTton Click - sent back when user clicks a button
{
byte Size; // 8
byte Type; // ISP_BTC
byte ReqI; // ReqI as received in the IS_BTN
byte UCID; // connection that clicked the button (zero if local)

byte ClickID; // button identifier originally sent in IS_BTN
byte Inst; // used internally by InSim
byte CFlags; // button click flags - see below
byte Sp3;
};

// CFlags byte : click flags

#define ISB_LMB 1 // left click
#define ISB_RMB 2 // right click
#define ISB_CTRL 4 // ctrl + click
#define ISB_SHIFT 8 // shift + click

// If the TypeIn byte is set in IS_BTN the user can type text into the button
// In that case no IS_BTC is sent - an IS_BTT is sent when the user presses ENTER

struct IS_BTT // BuTton Type - sent back when user types into a text entry button
{
byte Size; // 104
byte Type; // ISP_BTT
byte ReqI; // ReqI as received in the IS_BTN
byte UCID; // connection that typed into the button (zero if local)

byte ClickID; // button identifier originally sent in IS_BTN
byte Inst; // used internally by InSim
byte TypeIn; // from original button specification
byte Sp3;

char Text[96]; // typed text, zero to TypeIn specified in IS_BTN
};

First wheel went belly up; stopped responding and just displayed the 8.8.8. Additionally, it had the off center issue. Didn't bother me while racing, but still another issue worthy of replacement.

Second wheel, which was a step back since they sent me a beta wheel. One of the mounting plates inside the wheel was loose and floating around inside the wheel. Who knows if it caused any damage to the internals. But I was unable to mount it to my cockpit, and since it was a replacement I wasn't going to take any chance with internal damage.

Each time I included either a video or pictures with my RMA request. Each time there were no questions asked and a replacement unit shipped as soon as possible.

My first set of pedals never held calibration. If I wanted to use them I needed to calibrate them each time I wanted to race. Very inconvenient. The new electronics that they sent were to fix the throttle/clutch issue.

Like I said, they may be slow in responding, but they will take care of you once they acknowledge your problem.

Quote from brt900 :

ahhh i wonder if i do get new pedals.

You'll get just the wheel replaced.

I am on my 3rd wheel and 2nd set of pedals. Plus, they sent me all new electronics for the pedals. Fanatec support is slow to respond, but they will take care of you.

Canada vs. Russia 7:30PM EST. Depending on how the game is going I may miss this one. No disrespect, but I am pulling for Russia. Ovechkin and Semin are my boys from the Caps.

Anyways in the 3 laps I have done so far my best is 2 minutes. Funny how much speed those walls can scrub off your car, not to mention the damage to the paint job.

Quote from brt900 :

anyone got a decent south boston advanced legend setup only one i found was the easy to drive setup but way too slow

Link to Team Redline - Gregor Set: http://www.teamredline.co.uk/file/setups/42/

Set is old, but still maybe decent. Haven't tried it myself.

Now I know who to concentrate my dagger eyes on. :gnasher:

Quote from Danke :

Please don't tell me I'm 2 seconds of the pace. :|

Ah, the steel walls of South City.

I haven't run any laps yet, so your are way ahead of the field.

Quote from Danke :

b) severe car damage, although any driver doing so must convince his national hockey team to throw their Olympic game against team USA

That was a low blow.

Perfectly acceptable in my book. I like the Jerk Chicken story better, but honesty is the best policy.

Quote from brt900 :

where do i actually put the setups and on game which section in garage do i load them

first part: http://www.answers-script.com/iracing/article.php?id=77

On the right side of the Garage there are tabs loading/saving/sharing.

My Rusty Screw nomination goes to Jonathan. Me must have gotten some bad Jerk Chicken take-out. Both races he had to pull into the pit to take care of what I can only assume was some personal business after laying down some fast laps.

Quote from brt900 :

what are the requirements for class D and if i do them before im promoted to 3.0 rookie will i get promoted twice

Try reading the license FAQ: http://www.answers-script.com/iracing/category.php?id=10