A way to bring everyone together - CRT=3
#1

Here is my idea... I am sure is not the first one but maybe was not posted in IL-2 community yet.

How possible would be to make the game have a new set of CRT? A punkbuster of the people. What would be the purpose?

1. Opened buttons to community.

Advantages:
-people without knowledge to "cracking" that little nut but, with good knowledge of interpreting FM data could help improve faster the new flyables.
-faster communication between groups as the data would be in the open

2. Opened teachings for what other hidden tweaks, so many others could participate with ideas and mods without having deep knowledge of programming. Sometimes good ideas come by thinking outside the box... and best guy in thinking outside the box... is the guy outside of the box. Sometimes great ideas come from stupid questions from outsiders. Big Grin

3. Less fear of cheating and not playing on same "planet"


How would such thing be done? CRT=3

Facts known to "general public" (me included):

The FM/DM/WM are in the buttons file mainly.
Some FM I understand can be tweaked with some class files editing
Buttons file is a small one
Air.ini, weapons_ru.ini and plane_ru.ini etc... are small and important to be the same on both parts...server and client

Cheating... although very rare (or myth) can be achieved even in CRT=2 configuration with programs that monitors what IL-2 stores into memory and modifying directly there the sensitive data.

One example of such benign software some of us use is San's IL-2 FOV changer. I can join any CRT=2 server with it and no one will notice a thing.

Some possible cheats are tolerated as is... like modifying the textures from opened mods to see through them... such cheats are seen as lame and are being healthy dismissed.



So...

How about making the IL-2 to have the server imposing the rules? Or check them very good. Or both?

How about making the server either "inject" to the client at mission transfer the buttons contents it uses and the important .ini files? Once the player disconnects he reverts to his versions of the files thus he is free to mod them as he please but forced to respect a common set of world rules when plays online.
How about making the server checking from time to time what version of sensitive data for the plane player flies? Directly from RAM. At variable intervals. A first recheck should be done when player starts his engine. And if differences are found then server could either resend the data, either impose a power penalty to that player... say 70% power so he can barely reach home base then refly if already in air or, cut off engine(s)(thus force a recheck/resend at mid air restart).


Why I say these...

I noticed that the actual sensitive data of IL-2 is quite small in dimension so it could be send via internet link quite quick. The buttons contents and ini's could be send at mission loading and the checking should be made only for the plane the player flies.

Sensitive hash files could be send also to the client. Maybe at server choosing.

With some of the moders in "Team Daidalos" maybe a good help from Oleg and Co can come in this direction.

With this I find many improvements on both things... anti cheating and openness of the game thus further development. Sure there could be difficulties but with so many minds at work they can be overcome.

What do you say? Who has a better idea?



========

We would need also an application for distributing the mod packs better and updating them more often. This application should be client/server but should use torrent protocols. The server admins should update the files of the torrent pack... then a file list should be generated... then a torrent file is uploaded to a public tracker. The client verifies if he has in his mod kit pack the same version... when is informed by server that changes did occurred it will do a recheck on the same torrent location but with the new torrent... thus downloading only what is new. As log as the client stays in the pool it serves via torrent others with the needed parts.

In the end... the user uses a simple synchronizing tool to sync his game with the modpack.

If the application would give more control to the user he could either download or install only the non essential mods he likes but still helps the others with the transfer of the full torrent.


I took the liberty to post the same thing on all three major moding forums where modpacks are generated.


http://www.sas1946.com/main/index.php/t ... l#msg22963


http://il2ultrapack.net46.net/index.php ... ml#msg9711
Reply
#2

I have no idea how the modding works for IL-2 so I cannot offer a well informed opionion. I do have, however, a lot of experience with online gaming and have been driven out of playing at least one game (Battlefield 2) by excessive cheating on the servers. Yes it happens, no, it is not a myth. Will it happen to IL-2 if the possibility to cheat is made easier? No idea, I have no clue what is going on in the head of cheaters who delight in winning without any skill.
I understand and support the idea of a standard baseline identical for all players (and why not use that which everyone has anyways, the original planes). My question is, why not adher to that rule? You want a modded "original"? Just put it in its own slot. Where is the problem with that? Everybody can use their modded planes and we still have the common baseline. Either I am terribly dense and misunderstanding something or I have yet to see a reasoning of why the baseline should be abandoned. Memory cannot really be an argument in a game as ressource-hungry as this one (if you want good graphics).
Party on!
Reply
#3

zaelu Wrote:I took the liberty to post the same thing on all three major moding forums where modpacks are generated.


http://www.sas1946.com/main/index.php/t ... l#msg22963


http://il2ultrapack.net46.net/index.php ... ml#msg9711


Not quite. You seem to have ignored HSFX, where the work to re-encode the .SFS files and base on 4.09m was undertaken. (Ultrapack is little more than HSFX with additions).
Anyway, I don't think you'll have long to wait for the unified modpack, bearing in mind that HSFX was compiled with input from AAA, SAS and Ultrapack.

Besides, what your idea hasn't considered is the format of the modpacks, where any user can add new planes and mods as and when wished using the JSGME switcher. Thus everyone will have a different 'version'.
Anyway, for online purposes all the server host has to do is state which mods must be set on or off with JSGME in order to join. Any deviation from this and you CAN'T join - it already works as those flying on the 102nd server have found out. No need for more CRT.

:cheers:
Reply
#4

I am not a member of HSFX forums. I know about their works although I got in touch only with the 4.0 version. I didn't post at their forums as I thought it could be consider a bit rude as a first post. I hope they are also visiting these 3 forums and mix my I ideas with their own which I'm sure they have.


As for the other paragraph... if I set CRT=2 is a sure thing you can't join my server Wink .


Lets focus on the main ideas...
Reply
#5

Quote:I don't think you'll have long to wait for the unified modpack, bearing in mind that HSFX was compiled with input from AAA, SAS and Ultrapack.

This might answer your question: viewtopic.php?t=22941&postdays=0&postorder=asc&start=0. See monguse's post about six down. Unification is almost upon us and HSFX the tool used for it.

:cheers:

PS We wouldn't have minded your first post being about your idea; all suggestions welcomed!
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)