Doc. Caliban Posted October 21, 2009 Posted October 21, 2009 I'm sure this can be done in a similar way that the positioning for the helmet mounted sight can be changed. I use a cougar and the Antenna wheel for zoom. I like the zoom to be a tad less than the default, but leaving the wheel in any position other than centered causes the view to jitter every now and then. Any help would be greatly appreciated! -Doc [ Asus Rampage II Extreme | Intel i7 920 @ 3.6GHz| 12GB DDR3 | 3-Way SLI (3x GTX280OC 1GB) | 300GB Raptor | SupremeFX X-Fi 7.1 audio | 1,200W Thermaltake Toughpower PSU | 30" LCD @ 2560x1600 | Thrustmaster HOTAS Cougar | TrackIR 5 | CoolerMaster HFC 332 case ]
Butcher59 Posted October 21, 2009 Posted October 21, 2009 Try to change in the snapview.lua the following entry Snap[9][13]["viewAngle"] = 89.777544238285 I searched other forums and if i'm not wrong, it could be changed here. CPU: Intel i7-5820K 3,3GHz Motherboard: ASUS X99-A Grafik Card: NVIDIA Geforce GTX1080 Ti 337.50 RAM: 32GB PIMAX 5k+ BE Hotas Warthog with Simped Pedals WIN 10 64bit DirctX 11.0
Doc. Caliban Posted October 21, 2009 Author Posted October 21, 2009 Thanks, Butcher. I figured it was in there, but I had no idea which entry it was. I appreciate your help and will report back once I get a chance to try it. (probably this weekend) -Doc EDIT: Why do they carry the decimal places out so far? [ Asus Rampage II Extreme | Intel i7 920 @ 3.6GHz| 12GB DDR3 | 3-Way SLI (3x GTX280OC 1GB) | 300GB Raptor | SupremeFX X-Fi 7.1 audio | 1,200W Thermaltake Toughpower PSU | 30" LCD @ 2560x1600 | Thrustmaster HOTAS Cougar | TrackIR 5 | CoolerMaster HFC 332 case ]
Kuky Posted October 22, 2009 Posted October 22, 2009 EDIT: Why do they carry the decimal places out so far? I've wondered this as well, the little programming I've done back in uni I would have thought the more decimals you set the higher precision of the calculations, the more processing power it takes :noexpression: 1 PC specs: Windows 11 Home | Asus TUF Gaming B850-Plus WiFi | AMD Ryzen 7 9800X3D + LC 360 AIO | MSI RTX 5090 LC 360 AIO | 55" Samsung Odyssey Gen 2 | 64GB PC5-48000 DDR5 | 1TB M2 SSD for OS | 2TB M2 SSD for DCS | NZXT C1000 Gold ATX 3.1 1000W | TM Cougar Throttle, Floor Mounted MongoosT-50 Grip on TM Cougar board, MFG Crosswind, Track IR
Waldo_II Posted October 22, 2009 Posted October 22, 2009 I've wondered this as well, the little programming I've done back in uni I would have thought the more decimals you set the higher precision of the calculations, the more processing power it takes :noexpression: Significant maybe if you are writing software for an Apple II, but not today. High-end software will almost always use floating-point variables, which are high-accuracy numbers. In writing software there are different types of numerical variables depending on what language you are using. Typically there are at least integer variables and floating-point variables. If you are writing software that calculates the effect of air pressure and tempurature on rotor lift and happen to come across a FOV setting, it is easy to type "float defaultfov" instead of "int defaultfov." DCS may also calculate the default FOV based on a variety of settings, such as resolution, screen aspect ratio, monitor setup, etc. You may have come across a combination that gave you a such a strange setting.
Recommended Posts