Sounds like this is needed as an InSim Packet. So we know ... might be a good idea to make an RFC for that information.

Quote from T3charmy :

I may add another parameter to the function that allows it to be only sent to servers running the calling plugin.

That is pretty cool dude! Very nice work!

Love what you're doing with the tagging of release on GitHub. Awesome job, very clean!

Adds a feature, 0.5.1.

Yes!

This is what I sent to T3 the first time he did it. As you have merge access, you all you would need to do is download the zip file from the github.

--

Quote from T3charmy :

What exactly needs to be done for next release? I know the Version Number needs to be updated(Need to add Jay and I to the authors, what else?

I update the version number and add Jay, submit the pull request to me. Once you've done that, I'll merge it. Once I've merged it, download the ZIP file from github for the master branch. This will give you a clean install of PRISM that you can release.

Quote from T3charmy :

I'm not exactly what all was changed between 0.4.4 and 0.4.5, but I guess I could look into that.

I look at the commit history between 0.4.4's release and the release that I'm putting out. From there I just use the commit information that I find interesting, or important. Like adding the name for a timer is a BC break, and must be mentioned in the change log.

Quote from T3charmy :

Do you want me to create the forum for it? not sure what exactly you wanted me to do.

You have to do two things at once. This is the process that I go through. Reply to PHPInSimMod - PRISM Releases. In the reply to that thread title the reply "PHPInSimMod (PRISM) 0.4.5". Then you have to include the change log from version 0.4.4 to 0.4.5. Attach the ZIP file to this thread, that contains clean installation of PRISM 0.4.5. That means no config files, except for the examples. Don't hit the reply button yet.

Then once you've done that, open a new tab in your browser and make a new thread in PHPInSimMod - PRISM Sub-Forum. In this your going to write

Quote from Post Template :

You can download PHPInSimMod - PRISM 0.4.5 from that link. Please use this thread to talk about this release.

Thank you.

And then attach the change log list that you put into the other thread. Once you've done this, go back to the Releases reply and hit submit and copy the URL and make the "PHPInSimMod - PRISM 0.4.5" text a link to that thread. Hit submit.

Sticky 0.4.5's thread, and un-sticky 0.4.4's thread.

Wanna make up release for that? 0.5.1?

It says your name is not available to be PMed.

Quote :

The following usernames were not found :

Victor

--

Can you please add PoVo as a Moderator to the PRISM Forum and Sub-Forums.

Quote from T3charmy :

@Dygear is this supposed to be a struct or a class on this line: https://github.com/Dygear/PRISM/commit/c6e75149d1aa80ab7252a0b19c51082263fb7b8d#diff-dc3f96ff17b9c36fec68c4e4e7ea23bcR1919

Class. I'm a moron.

SplStructs if you want to be really fancy.

T3 your my hero!

Woo! I did some checks to PRISM as pertains to PHP 7 compatibility. Good to see I'm not crazy.

If you delete your config files and then start PRISM, it will generate the config files for you and allow you to select all of the options you want in ISP_ISI.

Congrats on being the first "Approved" Plugin.

Quote from PoVo :

I also had to modify the pack() method in the Struct class similar to cargame.nl:

The line "if (!isset($packFormat[++$propertyNumber])) break;" is needed because PRISM will try to pack the StartObject property even though there is no pack format specified in PACK for it and ends up complaining about a non-existent index.

For me this seems the cleanest solution thus far but I'm wondering if someone can write it any cleaner?

You shouldn't modify the class function that work's everywhere's for one special case. What you should do, is overwrite that function in the special case only. That way, the special case code is only called when it's needed.

Quote from PoVo :

Dygear included the unpack() method in his latest commit. I don't think it's required because LFS doesn't send any IS_JRR packets. IS_JRR is only used for join request responses so it will only be packed.

That's because I'm an idiot and didn't read what the packet was for, I just implemented the packet as far as the structure goes.

Quote from cargame.nl :

Right.. Hmm .. So something like this?

https://github.com/Dygear/PRISM/commit/692730ef48f8434ba6d60b90e1859f6ec926e762

Kinda, if you could make a pull request out of that commit I'll be able to merge that into PRISM's master and you won't have to manually patch when you upgrade to the latest version on PRISM.

(And there is going to be a new release once the K patches become official.)

Quote from Scawen :

Am I missing something or is there no way to stop an object floating after you have used the Z adjuster?

In other words, a way to make a blue object selection button go back to orange?

That awkward moment when you forget how your software works.

(I have no idea how PRISM works at this point. I'll admit it.)

Can't reproduce on Windows 10, with PHP 7.0.3 x64, NTS.

I half agree with that. No ... Ok ... I agree with it. Take InSim away from the Demo Users.

Quote from DarkTimes :

sending packets in batches simpler. Now you can just do this:


<?php 
insim.Send(
    new IS_TINY { ReqI=1, SubT=TinyType.TINY_NCN }, 
    new IS_TINY { ReqI=1, SubT=TinyType.TINY_NPL }, 
    new IS_MST { Msg="Hello, world!" }
);
?>



Sending multiple packets in a single Send call uses less bandwidth than sending them individually. You should always look for ways to batch send your packets.

That's **** awesome!

Can we get an inline code block Vic? Pretty please? With sugar on top?

Quote from Scawen :

I don't think that would be a trivial update, because of the complexity of it. The slipstream effect is calculated as a contribution of a varying air speed vector in a stretched oval behind the lead car(s) combined with the actual wind speed. It can vary from a tiny amount to a large amount depending on several factors.

It's possible it could be boiled down in some way, but that depends on what you want to use it for.

EDIT: To me it sounds more like something that could be in the MCI packet. Something like "amount of slipstream" or "similarity to driving in a vacuum" though I haven't looked into how that could be calculated.

How do you calculate the amount of drag that is removed from each aero feature on the car? Shouldn't you be able to use the same calculation as the basis of scale?


We can then use this as a basis for any value of > 0.0 is a car that is receiving a draft and other programs that want to threshold this information could use anything above 0.20 as the basis for DSQing the lap.

--- Edit ---

Odd request perhaps. But once you start an InSim instance (by the command /insim=$port) could it send a ISP_ISI packet on loopback? Kinda like "Hey, I'm here." I leave my InSim instance running, in the background even when I disconnect and close LFS. If it could automatically reconnect once the LFS instance of InSim is ready that would be cool. Useful when debugging, I think.

Last edited by Dygear, Fri, 5 Feb 2016 08:44.

Should always use the wizard! Vic did a fantastic job on that part of PRISM.

I may "borrow" some of this code for the Timing&Scoring plugin.

Just submit a pull request with your changes. And Git will merge the rest.

Like Povo did here.

Last edited by Dygear, Fri, 5 Feb 2016 06:22.