Page 5 of 14

Posted: 11 Apr 2011, 00:57
by majkelgb
I cannot tell how :)

Posted: 11 Apr 2011, 01:22
by EyTschej
Mouse sensitivity scale of "Default Player" and my own created player uses a different scale, e.g. "Default Player" (in practice mode) is totally hyper-sensitive at 3.0 and I use 1.0 (anything else is way too sensitive, just like in beta 1), but my own created player has a pretty low sensitivity at 3.0 already (I currently use 2.2). So the problem here is, that the Default Player seems to be stuck in beta 1?!? So I can't really use practice mode because I would always have to jump totally different due to the high sensitivity.

Suggestion: Add option to practice mode, which player should be used (so the created player can be chosen - that should fix the problem with the Default Player the easy way).

Posted: 11 Apr 2011, 02:05
by Kettger
I think lighting in the evening hills [notably Lahti] is insufficient. I play in 1920x1080, 32BPP and AAx4 and I can't observe a spot of threshold. ;P

Posted: 11 Apr 2011, 09:32
by Jussi Koskela
EyTschej wrote:Mouse sensitivity scale of "Default Player" and my own created player uses a different scale, e.g. "Default Player" (in practice mode) is totally hyper-sensitive at 3.0 and I use 1.0 (anything else is way too sensitive, just like in beta 1), but my own created player has a pretty low sensitivity at 3.0 already (I currently use 2.2). So the problem here is, that the Default Player seems to be stuck in beta 1?!? So I can't really use practice mode because I would always have to jump totally different due to the high sensitivity.

Suggestion: Add option to practice mode, which player should be used (so the created player can be chosen - that should fix the problem with the Default Player the easy way).
There's separate sensitivity setting for the practice mode (it's not using the 'default' player).
You can find it in Practice -> Settings -> Mouse Sensitivity.

Posted: 11 Apr 2011, 10:38
by J.MIRO
Im dont know, whether it was already discussed, but past its sell-by date.
In repleys, one can't see the starting beam.
What is happening?

Posted: 11 Apr 2011, 10:46
by EyTschej
Jussi Koskela wrote:
EyTschej wrote:Mouse sensitivity scale of "Default Player" and my own created player uses a different scale, e.g. "Default Player" (in practice mode) is totally hyper-sensitive at 3.0 and I use 1.0 (anything else is way too sensitive, just like in beta 1), but my own created player has a pretty low sensitivity at 3.0 already (I currently use 2.2). So the problem here is, that the Default Player seems to be stuck in beta 1?!? So I can't really use practice mode because I would always have to jump totally different due to the high sensitivity.

Suggestion: Add option to practice mode, which player should be used (so the created player can be chosen - that should fix the problem with the Default Player the easy way).
There's separate sensitivity setting for the practice mode (it's not using the 'default' player).
You can find it in Practice -> Settings -> Mouse Sensitivity.
Even more mouse settings? Hmmm ... Jussi, seriously: This is a little confusing. Back in the days, you used one mouse setting in "SETTINGS". I understand that it was a good idea to introduce individual mouse settings per created player, but yet another mouse setting in practice mode itself ... it's getting confusing. Maybe back to my suggestion? ;)

Posted: 11 Apr 2011, 11:22
by Michs20

Posted: 11 Apr 2011, 11:26
by Jussi Koskela
EyTschej wrote: Even more mouse settings? Hmmm ... Jussi, seriously: This is a little confusing. Back in the days, you used one mouse setting in "SETTINGS". I understand that it was a good idea to introduce individual mouse settings per created player, but yet another mouse setting in practice mode itself ... it's getting confusing. Maybe back to my suggestion? ;)
The setting is just in different place than it used to be in DSJ3. It was the same already in beta-1. This way it's easier to find a suitable sensitivity in the practice mode without going through different menus.

Posted: 11 Apr 2011, 15:07
by pikuvava
can skis text change???
can anyone how? tell if can.

Posted: 11 Apr 2011, 16:34
by m00nchile
I wouldn't call this a bug per-se, but it's still a bit of imbalance. Mainly, the style mark system seems to be a bit too lenient. In Kulm, the max distance where you can land a telemark is about 209m, if you get a good flight curve (shallow, not a lot of height), there the jumper barely stands, but I still get 19.0 or even 19.5, where in reality such a landing would get 18s max. It's pretty usual that the winning player has two jumps of about 206m, but the jumper who gets two 210+m efforts in loses because of the two-footed landing.

TL;DR: the style mark system should take into consideration if the jumper barely held the landing and award apropriate style marks.

Posted: 11 Apr 2011, 16:59
by jjannee
[quote="Jussi Koskela"][quote="EyTschej"]
Even more mouse settings? Hmmm ... Jussi, seriously: This is a little confusing. Back in the days, you used one mouse setting in "SETTINGS". I understand that it was a good idea to introduce individual mouse settings per created player, but yet another mouse setting in practice mode itself ... it's getting confusing. Maybe back to my suggestion? ;)[/quote]
The setting is just in different place than it used to be in DSJ3. It was the same already in beta-1. This way it's easier to find a suitable sensitivity in the practice mode without going through different menus.[/quote]

When comes rest of hills? Planica, Vikersund ym.?? =)

Posted: 11 Apr 2011, 17:03
by Jan Šterba
After few minutes (app. 2-3) the game starts lagging very much without any reason... my PC is quite good, so the problem is not there... What can be done with that? Detail changing doesn't change that.

Posted: 11 Apr 2011, 17:21
by dzamper
Image

Tree in the house :o

Posted: 11 Apr 2011, 17:23
by Risto Salonen
Jan Šterba wrote:After few minutes (app. 2-3) the game starts lagging very much without any reason... my PC is quite good, so the problem is not there... What can be done with that? Detail changing doesn't change that.
Try switching sounds off in the game setup.

Posted: 11 Apr 2011, 17:51
by magnevox
Some bug with F9 camera.
Image