So you need to replace them with dummy files.ĭon't forget to make backups of files you will replace!Ĭopy dummy qb_scripts.pr* files from archive's Data\pre folder to the same folder in you game's folder, replacing original files. But it looks like the game is reading compiled scripts files first. The solution to this is to remove blur functions from script files.
#D3doverrider windows 10 2016 windows#
These files is this solution compiled by me.įor some reason, on Windows Vista and later, blur (in main menu, during Focus and so on) is bugged, making it nearly impossible to see anything during that blur.
Worked on between 2015 and sometime early/mid 2016. do so at your own risk.Īlso shoutout to ParkourPenguin of the CE Forums for cleaning up my messy but working AA script into something neat and tidy. I haven't tested this online and don't plan to since i'm not going to risk my Punkbuster status on it either. Okay, all tech stuff out of the way? good. Shoutouts in any possible outside implementation would be nice but not required.
#D3doverrider windows 10 2016 free#
You are also free to examine how this works and possibly work it into your own implementation outside of CE. You are free to modify the AA script to change the condition numbers to see the effects listed in the explanation. Multiple results will show up that have the same value but I created this in the first place to avoid any messing about unless you really are just curious (like i was). To verify these numbers yourself, Load up CE and do a float search for the FOV listed with your state.
Sprint varies but tends to increase FOV dramatically past 51, sending any attempt at modification haywire. Personal Current Preference of modifier numbers are anywhere between 28-30, thus forcing the 51 of standing fov up to around 79-81.įor the curious, The standard numbers for multiple states as stored in game memory:Ĭrouched ADS (with or without Reflex) 33.16657257 What is unknown to me as the author of this CT is if the FOV being referred to is Horizontal or Vertical. This is separately changeable to allow for the player to reduce camera issues with leaning. The lean check number of 41 is to prevent similar camera issues as described with sprinting when you are leaning from cover. The drawback of having these numbers as the limits is the obvious "change" when you change from one viewpoint to another.
When you modify any of the sprint numbers past 52, the sprint camera draws out backwards far too much to be usable. Sprinting usually sends the camera FOV past the standing FOV of 51 into the 53+ range. Going any lower leaves any ADS modes unusable due to lack of zoom.ĥ2 being the highest desirable number to modify. This works by checking if the FOV as stored in game memory meets the condition of being between 39 and 52 (also checking if leaning).ģ9 being the lowest desirable number to modify.
0 kommentar(er)
