Can someone confirm that Outgauge/Outsim work in patch X when initialized?

I get "outGauge : enabled" and "OutSim : enabled" in LFS but I don't receive any packets

Check your cfg.txt if you initialize Outsim / Outgauge via Insim. It seems like the Settings in cfg.txt have Priority over what you set over Insim. This was my Error when I had the same Problem like you have now... maybe it´s the same.

you should have told scawen before X ;p

it's probably simply ignoring the insim ports when activated through insim
"// The OutGauge packets will be sent to the UDP port specified in the InSimInit packet." Only getting NLP and MCI over that port (or all using udp only)

Did anyone else tested this or did succeed in receiving out* without modifying the config?

As I understand it, Out(Sim|gauge) packets come over via UDP, rather than TCP - even if you connect via TCP - would that explain it for you?

I tested it. Outgauge works fine in patch X, without modifying any cfg-file.

Do you await OGpackets on the in the IS_ISI specified UDP-port?
Is it possible that your code only seldomly gets executed because of some blocking calls (I know several libraries where the TCP-receive call is a blocking call).

But beside that: Does anyone know why sizeof(OutGaugePacket) yields a size of 96 bytes, but the actual OGP is only 92 bytes long?

Vain

Nope, as it's not even working if I "only" use udp for insim. And if you use only udp the outgauge packets should arrive on the same port as all other packets. Or if you use TCP and set a UDP port they should arrive on that port like the race tracking NLP/MCI do.

edit: above is resonse to angel.

Quote from Vain :

But beside that: Does anyone know why sizeof(OutGaugePacket) yields a size of 96 bytes, but the actual OGP is only 92 bytes long?

If it's unchanged since pre-InSim v4, the last int variable is optional and only actually sent if you set a request id - this accounts for the 4 bytes difference in size

Quote from Vain :

I tested it. Outgauge works fine in patch X, without modifying any cfg-file.

Do you await OGpackets on the in the IS_ISI specified UDP-port?
Is it possible that your code only seldomly gets executed because of some blocking calls (I know several libraries where the TCP-receive call is a blocking call).

As written; Testing with udp only and with tcp returns the same result...

I'm sending the following to lfs.
Connected with local port: 1831
UDP ->: 2c 01 22 00 27 07 10 00 00 00 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 54 65 73 74 00 00 00 00 00 00 00 00 00 00 00 00
ISI with the local port set and lfs displays the port in brackets ingame.
UDP ->: 08 04 22 02 00 00 00 64
The ISI small of type SSG and delay of 100ms and LFs displays "Outgauge: enabled"

But I only receive the isp ver and the race tracking packets.
UDP <-: 14 02 22 00 30 2e 35 58 00 00 00 00 53 32 00 00 00 00 04 00

Quote :

But beside that: Does anyone know why sizeof(OutGaugePacket) yields a size of 96 bytes, but the actual OGP is only 92 bytes long?

Vain

The optional ID at the end is not send if you initialize it through insim iirc.

Oh wait that should be
UDP ->: 08 04 22 02 64 00 00 00, not?

Hm doesn't matter. Wont work

Are you 100% sure you disabled Outgauge in the Config File? This was my fault when I tested with Insim V4... I enabled it in the Config File.
Maybe you can install Wireshark on your LFS Machine and watch if LFS even sends Outgauge Packets (you then will see too to which IP / Port they are sent).
For me it´s working perfectly in Patch X with my PocketLFS App. And I enable Outgauge via Insim too (and leave the Config File untouched now).

OutGauge Mode 0
OutGauge Delay 100
OutGauge IP 127.0.0.1
OutGauge Port 1968
OutGauge ID 0


mh okay if it works i have to find my error ^^

I'll try with wireshark later

Ok first testing results

• If you don't close outgauge on disconnect it keeps sending data to port A and if you connect with an other port B and enable outgauge it keeps sending to the port A of the first connection instead to port B.
  
• race tracking with value of "100" equals a SMALL_SSG value of 10...
  compare: // OutGauge Delay 1 :minimum delay between packets (100ths of a sec)
  with: // Time in ms between NLP or MCI (0 = none)
  => confusing!
  
• The source port of the OG packets is not the same as the port of the other packets -> my udp socket was connected to that port and didn't listen to packets coming from other ports -> no og ^^
  

Works now

Nice! You got it working finally. Congratulations and happy coding