Thank you for v1.45!

[heyvern69 22]

This is my official "Thank You" to BIS for the last patch, version 1.45.  You addressed the major problems with joystick & throttle response, and I for one, really appreciate it.

Flying planes & helos with throttle & stick is really fun now.  Keep up the great work!

You've really got the "soldier" perspective nailed down tight.  So keep up the good work on improving the flying experience (More planes, more types of helos, better visibility [less fog], improved flight dynamics, etc.), and the network code improvements too (Dump DirectPlay).

   

[ALDEGA 0]

"better visibility"

put "setviewdistance 5000" in an init field (or any script field). See the result.

[heyvern69 22]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (ALDEGA @ Mar. 02 2002,23:25)</td></tr><tr><td id="QUOTE">"better visibility"

put "setviewdistance 5000" in an init field (or any script field). See the result.<span id='postcolor'>

2 Questions:

1) How (I don't even make my own missions. I have never so much as opened the editor).

2) Does this only affect a single mission, or will it affect the whole game (campaign, single player missions, multiplayer missions, the whole thing???)

I heard of this trick, but I thought it only worked when you were creating a mission. I didn't bother, because I don't create missions. But IF I can do this once, and have all future single and multiplayer missions use that increased "setviewdistance", then I will certainly do it right NOW.

-Vern.

[WKK Gimbal 0]

It has to be in a trigger, inside the mission.

Basically, you set Condition to True and in the Activation field write: setviewdistance 2000

You can also make it so it benchmarks OFP's graphics settings and adjusts the value accordingly, so slow PCs can play the mission too. But this also needs to be in a trigger.

[ALDEGA 0]

works in scripts and init fields too