That's not a bad idea. I like flexibility in general.
One thing, for every new idea, it should be in it's own thread with the title [RFC] and then a one line description of the idea.
One thing, for every new idea, it should be in it's own thread with the title [RFC] and then a one line description of the idea.
Your other option is single player, and that's where I do most of my practicing.
OutGauge is only for local information. You'd have to have every client on the server route their OutGauge packet information to your OG / InSim client. This _can_ be done, however, it most cases setting up OutGuage is not a part of the expected setup for a race. The best bet would be a IS_CSC packet for CarStateChange, where it could notify the server of a change to the car such as break bias or traction control turning on / off.
Something along the lines of the OutGuage Packet into a InSim Packet.
Something along the lines of the OutGuage Packet into a InSim Packet.
struct IS_CSC
{
byte Size; // ?
byte Type; // ISP_CSC
byte ReqI; // 0
byte PLID; // player's unique id
word Flags; // Info (see OG_x below)
byte Gear; // Reverse:0, Neutral:1, First:2...
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
};
Last edited by Dygear, .
24 fps is the minimum that anyone can watch and get the sense of continuous motion, going from 24 to 30 fps is not that much better, but from 30 too 60 fps is a pretty big leap in visual fidelity for me at least. Going from 60 too 120 is pretty much perfect as to what my eyes can perceive and I've not noticed any change to an image generated from 120 too 144hz and I've not seen any true 240 hz screens with 240 hz content so I can't say much about that.
Max: 1001 FPS
Avg: 975.022 FPS
Min: 749 FPS
When you say you've maxed everything? Does that include the DSR (Dynamic Super Resolution) setting, what is that set to? I would love to know if your rendering at 4k but then downscaling too 1080p. If your getting that FPS with the DSR setting on, that would be amazing. What's the rest of your system specs for reference?
Avg: 975.022 FPS
Min: 749 FPS
When you say you've maxed everything? Does that include the DSR (Dynamic Super Resolution) setting, what is that set to? I would love to know if your rendering at 4k but then downscaling too 1080p. If your getting that FPS with the DSR setting on, that would be amazing. What's the rest of your system specs for reference?
Last edited by Flame CZE, .
Victor, can you please fix tabs being stripped out within the [code] tags. It's making quite a bit of my code look ugly. (Besides the code it's self looking ugly, ergo it needs all the help it can get.)
I've requested Moderator power for the Programmer Forum, hopefully I'll be able to do it. Otherwise I'm hoping that a current mod will pick up the change. And I should be able, built the next RFC regarding getting IP address from Scawen's remarks now that we have a direction.
I'd love to split this topic now. As we are talking about two different things and should be two separate RFCs.
That would be an improvement over the current system for sure.
That's what I wanted to discuss with you about. How is it defined in the engine what language a user selects? Can we take the information directly and just port it into a InSim Packet? Without knowing a lot about how the internal parts of the engine stores this information, we can only speculate as to the correct implementation.
Scawen, I can't PM you so forgive the off topic introjection, but do you check the programmer forum anymore? Could you direct your attention too [RFC] InSim Language Information
He's said it before.
I think Scawen would say that this is one and the same, but if they are being exposed via the log, then really there is no good reason to keep them away from the InSim application, as this information is already available programmatically albit in a roundabout way.
Victor, can you please fix tabs being stripped out within the [code] tags. It's making quite a bit of my code look ugly. (Besides the code it's self looking ugly, ergo it needs all the help it can get.)
Sp3 doesn't do anything, it's defined as a spare byte that was never used. It was originally there to pad the length of the NCN packet so that it would be divisible by 4 bytes (32 bits).
[RFC] InSim Language Information [implemented]
By replacing Sp3 in IS_NCN (NewCoNnection) with a byte called Lang to point to an enumeration of languages supported by LFS we can find out right away what language that client prefers.
What do you all think?
// Language Enumerations (for NCN's Lang byte)
enum
{
LANG_ENGLISH,
LANG_FRENCH,
// ...
LANG_NUM
};
struct IS_NCN // New ConN
{
byte Size; // 56
byte Type; // ISP_NCN
byte ReqI; // 0 unless this is a reply to a TINY_NCN request
byte UCID; // new connection's unique id (0 = host)
char UName[24]; // username
char PName[24]; // nickname
byte Admin; // 1 if admin
byte Total; // number of connections including host
byte Flags; // bit 2 : remote
byte Lang; // See Language Enumerations.
};What do you all think?
So how about this, in the Programmer's Forum, we make a thread for each feature we want as a poll. Should it make 50% of the vote in favor would you then consider it? There are a bunch of features that I think would make a great addition too InSim if we can get them onto the system. But we need you to be apart of that conversation.
Might of been better off using LFSWorldSDK for the basis of your program. Although, I admit that I might be bias.
You should also never use error suppression operator (@) as it's very slow and setting error reporting at run time should also be avoided if you're expecting your code to be included in other programs.
You should also never use error suppression operator (@) as it's very slow and setting error reporting at run time should also be avoided if you're expecting your code to be included in other programs.
At what point can we start discussing new packets and features for InSim?
Guys. This is not the place for a witch hunt. He found a bug in PRISM that I've now fixed. Shows over.
That would make for a pretty epic flowing section if they were connected with the same radius as shown.
Could we get an InSim Language Packet, or make it a part of the IS_NCN packet, like Use Sp3 for a Lang define. How many languages does LFS support, can it express that information in a byte (0 - 255)? This above all else would be a massive help to InSim applications.
FGED GREDG RDFGDR GSFDG