COD Infinite Warfare (IW) Rev 1.02

[UK_Wildcats]

Anyone have a working S Ravage/Rack 9 jitter working?

Not since they patched it

[bonefisher]

Anyone have a working S Ravage/Rack 9 jitter working?

Not since they patched it

They could at least made a lobby that only jitters could work and let them see how the rooms are full most of the time and then keep the cry babies out. lol!

[Bleak5170]

Anyone have a working S Ravage/Rack 9 jitter working?

Not since they patched it

They could at least made a lobby that only jitters could work and let them see how the rooms are full most of the time and then keep the cry babies out. lol!

The only problem is most jitter users don't want to play against other jitter users, lol.

[Raptor_Titan2]

Anyone have a working S Ravage/Rack 9 jitter working?

Not since they patched it

I have a model 2187 jitter that's better to use than rack9 in the library. Check it out and watch some youtube videos on it. It's very op.

[UK_Wildcats]

Anyone have a working S Ravage/Rack 9 jitter working?

Not since they patched it

I have a model 2187 jitter that's better to use than rack9 in the library. Check it out and watch some youtube videos on it. It's very op.

Thank you for sharing. I'll take a look at them

[Raptor_Titan2]

Ok

[UK_Wildcats]

Thank you Raptor. I'l take a look at it this weekend.

From an initial review, you have to be careful with vm_tctrl. This controls the main loop processing. Normally, you only put this in the main part of a loop and not within a combo. It should only appear once within the script and within the main loop.

The main loop is 10mS by default. The vm_tctrl variable is the delta amount to apply to this 10mS. For example, vm_tctrl(-1) is 10mS - 1mS = 9mS main loops. This means that the wait times will only correspond to 9mS intervals. In example, a wait of 10-17mS is the same wait of 18mS which is the time of 2 main loops.

A vm_tctrl(-0) does not do anything since the delta change is zero.

Because the jitter mod is so tight on timing, I recommend going to vm_tctrl(-5) for 5mS main loops or even vm_tctrl(-8) for 2mS main loops. You then adjust your wait times in the combo to correspond to the vm time.

VM_TCTRL vs Wait Time Fidelity
https://www.consoletuner.com/forum/viewtopic.php?f=6&t=5586&p=41799&hilit=vm_tctrl#p41799

Also, keep in mind the frame rate of the console. For example, the PS4 frame rate is 60 Hz which is 60 frames per second or 1 frame every 16.7mS. For gaming, this is very similar to the main loop of the Titan 1. The controller inputs may be seen by the PS4 but the game will only process it within a frame; therefore, controller inputs to the game will depend on when it occurs within the actual frame (beginning, middle, end).

For your jitter testing and modifications, you will get lots of variation depending on the actual wait times vs when the inputs hit within the actual frame.

[Raptor_Titan2]

Thanks man. That's part was added by Unjust_Zengetsu. But we both are just learning about that. I'll relay the message. That info will truly be helpful. Thanks alot.

[bonefisher]

A heads up not to use vm_tctrl(-9) because it causes overheating of the cpu. Can use vm_tctrl(-8) with no problems.

[Raptor_Titan2]

A heads up. Long story short I deleted all my scripts from both sites yesterday. I will be released uploading them later this week.