There is a soft stop at whatever setting your profiler is set to, soft stop meaning 100% FFB resistance at and beyond the rotation specified. LFS, however, does not (yet?) make use of the API provided by Logitech to change this on-the-fly to reflect appropriate settings for the car selected in-game, you have to set it up yourself.
Personally I have it set to 720° in the profiler and use LFS's wheel turn compensation, that way my ingame rotation range depends on the car, but the soft stops remain at 720°.
Personally I have it set to 720° in the profiler and use LFS's wheel turn compensation, that way my ingame rotation range depends on the car, but the soft stops remain at 720°.
I've never actually coded a local InSim app, but my take on this would be:
- Request a STA using TINY_SST
- check whether ISS_MULTI flag is set in STA.Flags
- If yes:
- Request all NCNs via TINY_NCN
- find NCN without remote flag set (Flags & 4)
- store the corresponding UCID
- request all NPLs via TINY_NPL
- store PLID of NPL associated with previously stored UCID
- Local UCID is 0, AIs can be identified via (NPL.Flags & 2)
The InSim way is as you describe, OutGauge gives you the speedo-readout (which isn't necessarily the actual velocity of the vehicle) and OutSim a velocity vector (which is the actual velocity of the vehicle).
Downsides to OG and OS are
Downsides to OG and OS are
- You cannot initialise them if they're configured in the cfg.txt (or in other words, if there already is an application using OG/OS).
- They lack an identifier, it is not possible to associate OG/OS packets with one particular player based on the packets alone.
While on the subject of road safety: I was wondering, is it true that US drivers share a general aversion towards seatbelts?
What the hell did you translate that with? Google shouldn't be this bad from EN to DE 
Just played it for the first time in years and you know what? It's 10 years old and looks better than GRID, Shift and all that other CM and EA garbage. Particles (smoke and sparks!), realtime reflections, excellent lighting, nice textures and no fckin ridiculous bloom and incorrect motion blur!
Granted, the kinematics and dynamics take some getting used to if you're all LFS-ified, but it's a great game nevertheless. My only problem now is that I can't find any of my memory cards
Granted, the kinematics and dynamics take some getting used to if you're all LFS-ified, but it's a great game nevertheless. My only problem now is that I can't find any of my memory cards
A couple of reasons why LFS is a PC title and will remain one for the foreseeable future:
- InSim
- OutSim
- OutGauge
- Decentralised, community maintained server structure
- As Woz pointed out, performance would almost certainly be an issue. The XB360 is, in theory, capable of processing 6 threads simultaneously, LFS's demanding physics, however, are single-threaded.
Realigning the cameras could be done via InSim, as well as selecting the same car the primary client is currently focused on.
AFAIK everything in Commands.txt can be used in scripts
I'm not familiar with CInSim but my guess is it's slightly outdated. The OutGauge structure was recently changed to hold dashboard lights in a separate bit field labled ShowLights.
As for using the indicators, use the keys 7 (left), 8(right) or 9(both, hazard warning) to turn them on and 0 to turn them off again.
// OutGauge - EXTERNAL DASHBOARD SUPPORT
// ========
// The user's car in multiplayer or the viewed car in single player or
// single player replay can output information to a dashboard system
// while viewed from an internal view.
// This can be controlled by 5 lines in the cfg.txt file :
// OutGauge Mode 0 :0-off 1-driving 2-driving+replay
// OutGauge Delay 1 :minimum delay between packets (100ths of a sec)
// OutGauge IP 0.0.0.0 :IP address to send the UDP packet
// OutGauge Port 0 :IP port
// OutGauge ID 0 :if not zero, adds an identifier to the packet
// Each update sends the following UDP packet :
struct OutGaugePack
{
unsigned Time; // time in milliseconds (to check order)
char Car[4]; // Car name
word Flags; // Info (see OG_x below)
byte Gear; // Reverse:0, Neutral:1, First:2...
byte SpareB;
float Speed; // M/S
float RPM; // RPM
float Turbo; // BAR
float EngTemp; // C
float Fuel; // 0 to 1
float OilPressure; // BAR
float OilTemp; // C
unsigned DashLights; // Dash lights available (see DL_x below)
unsigned ShowLights; // Dash lights currently switched on
float Throttle; // 0 to 1
float Brake; // 0 to 1
float Clutch; // 0 to 1
char Display1[16]; // Usually Fuel
char Display2[16]; // Usually Settings
int ID; // optional - only if OutGauge ID is specified
};
// OG_x - bits for OutGaugePack Flags
#define OG_TURBO 8192 // show turbo gauge
#define OG_KM 16384 // if not set - user prefers MILES
#define OG_BAR 32768 // if not set - user prefers PSI
// DL_x - bits for OutGaugePack DashLights and ShowLights
enum
{
DL_SHIFT, // bit 0 - shift light
DL_FULLBEAM, // bit 1 - full beam
DL_HANDBRAKE, // bit 2 - handbrake
DL_PITSPEED, // bit 3 - pit speed limiter
DL_TC, // bit 4 - TC active or switched off
DL_SIGNAL_L, // bit 5 - left turn signal
DL_SIGNAL_R, // bit 6 - right turn signal
DL_SIGNAL_ANY, // bit 7 - shared turn signal
DL_OILWARN, // bit 8 - oil pressure warning
DL_BATTERY, // bit 9 - battery warning
DL_ABS, // bit 10 - ABS active or switched off
DL_SPARE, // bit 11
DL_NUM
};As for using the indicators, use the keys 7 (left), 8(right) or 9(both, hazard warning) to turn them on and 0 to turn them off again.
I interpret "Photomode Competition" as a competition to make LFS look photorealistic, not to combine it with actual photographs. From my point of view, only genuine LFS screenshots should be used and enhanced to account for motion blur, depth of field, chromatic aberration, vignetting and whatever characteristics you can think of that make a photograph a photorgraph.
From InSim.txt
As you can see, IS_BTT is an info packet, which means it is always coming from LFS and never sent to it. LFS will send this packet when someone confirms (via "Ok") their input into a custom dialog window. This dialog is created by sending an IS_BTN with TypeIn set:
Note that to actually see the dialog, users have to click the button.
ISP_BTT, // 47 - info : sent after typing into a buttonAs you can see, IS_BTT is an info packet, which means it is always coming from LFS and never sent to it. LFS will send this packet when someone confirms (via "Ok") their input into a custom dialog window. This dialog is created by sending an IS_BTN with TypeIn set:
// 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"Note that to actually see the dialog, users have to click the button.
I'm not sure, personally I get bored with repetition quite quickly, even the most brilliant pieces of music bore the pants off me after a while. A change in quality can shift your attention to previously inaudible elements, so it's potentially less boring than the version you're used to.
I've recently started listening to the whole HVSC #52 (everything, include subtracks, 1m20s per track) in surround sound... it's vastly different from the original, mono SID experience on the (unmodified) C64. SIDs are definitely a lot easier to preserve, duplicate, distribute and play though, than vinyl that is
It's the iPood generation, the ones who call earplugs headphones, the ones who prefer(!) mp3 over uncompressed wave.
Luckily I was raised around vinyl, was taught what a good headphone or a good set of speakers sounds like and how to listen to music. Of course, nowadays nobody listens to music anymore, me included. Very rarely do I ever just sit back and listen.
Luckily I was raised around vinyl, was taught what a good headphone or a good set of speakers sounds like and how to listen to music. Of course, nowadays nobody listens to music anymore, me included. Very rarely do I ever just sit back and listen.
If you cannot find a cruise InSim application on this forum, nobody can help you.
I'lol'd
Seriously though, future is your best bet, just replace it all with a fireball
It says journeys, not car journeys, so my guess is the remaining 37% travel by foot (or a form of public transport, but that would make them passengers)
That right there is why I'm somewhat upset with Sony deciding not to go video for now. I'd love to use my constructively-damaged lenses for videos
I'm not sure I understand the question?
LFS uses DirectSound if that's what you want to know.
LFS uses DirectSound if that's what you want to know.
It comes with LFS, see docs/InSim.txt.
I said everyone who can afford the things (necessary to use LFS [online] in the first place) I listed
A freeloader, seriously? And you tell me something about not understanding the real world
FGED GREDG RDFGDR GSFDG