![]() |
|
Technical threads All discussions about technical issues |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
![]()
For those, like me, who couldn't read the list
Code:
Plane front side belly front side belly bf109g6 7,9 9,9 23 85,03 106,56 247,56 spit mk1 8 11,3 28 86,11 121,63 301,38 He 111 17,2 36,5 124 185,13 392,88 1334,72 |
#2
|
|||
|
|||
![]()
This thread is very interesting, I like the quantitative arguments. Manu and Tamat show a big love for CloD, otherwise they would not take the time and pain to do all the research, math and graphs
![]() My only concern is that probably the developers will drop all this good work down the pipe. Cheers! |
#3
|
|||
|
|||
![]()
If it doesn't comes is this sim, then maybe in the next one
![]() |
#4
|
||||
|
||||
![]()
This opinion takes much, much, much optimism, as insubers opinion takes pessimism.
__________________
Win 7/64 Ult.; Phenom II X6 1100T; ASUS Crosshair IV; 16 GB DDR3/1600 Corsair; ASUS EAH6950/2GB; Logitech G940 & the usual suspects ![]() |
#5
|
|||
|
|||
![]()
It shouldn't be so complicated to let the cpu do some small calculations for the visibility and use it for the distance DOT.
For the distance where the dot becomes a model, you could use the box of the whole A/C and calculate the angle according to the resolution and FOV. Also add a softer change from dot to model, by putting them on top of each other until the model becomes bigger than 6 dots in length equal which angle (horizontal/vertical). And to free it from "I can see you clearer in 640x480 Res" just make it lesser visible to the background (contrast) according to resolution. Which means the higher the Res, the higher the visibility one tiny dot. |
![]() |
|
|