Quote :

It would be really nice to have a key dedicated on keyboard that will represent some in-between state for both throttle and brake.

It's very possible. I recorded a short demonstration video: http://youtu.be/QWkWNqJwsOc. I'm using keyboard throttle and brake in this, but if you watch the pedal graphics, you can see that I can use several levels of both. I use PPJoy and GlovePIE to do this. Potentially, it's possible to have nearly unlimited amounts of stepping between minimum and maximum pedal input, as well as progressive sensitivity, automatic blip/cut, etc.

Fraps-based stuff does seem to be.. ambiguous. I've been recording frame latencies for AC for a while now. Shame that the ini files have some value for the physics rate, but changing it doesn't do anything

http://i.imgur.com/fZUdRny.jpg (2 laps around Magione).

Hysteria (Electric Violin Cover by Cait Lin) - Muse
http://www.youtube.com/watch?v=Kp5BWzLsgCE

Quote from NotAnIllusion :

Wibber needs to start intentionally costing Vetl as much time as possible, whenever possible. A good example was the T2 pass attempt. Vetel had forced him way of the racing line in 1. Instead of surging across the track to take a wide exit, just park it in the inside/middle and come to a near-complete stop, forcing Veetl to go to the outside. Then, take a normal wide exit and force him to either drive off the track or brake. Or, whenever Wibster is taking the inside line against Vettle, push him all the way to the white line every time instead of keeping it tight. If he turns in while on the outside, it's his fault.

http://media.theage.com.au/sel ... ff-the-track-4138013.html

Wibber needs to start intentionally costing Vetl as much time as possible, whenever possible. A good example was the T2 pass attempt. Vetel had forced him way of the racing line in 1. Instead of surging across the track to take a wide exit, just park it in the inside/middle and come to a near-complete stop, forcing Veetl to go to the outside. Then, take a normal wide exit and force him to either drive off the track or brake. Or, whenever Wibster is taking the inside line against Vettle, push him all the way to the white line every time instead of keeping it tight. If he turns in while on the outside, it's his fault.

Alonso drove into the back of a car, in a way that was completely avoidable. That is not good racecraft. Or maybe it is, for Australians.

1. Who will win? Alonso
2a. Who will take Pole? Vettel
2b. What will the pole time be? 1:36.071
3a. How many laps we will see behind Safety Car? 20
3b. How many safety car periods? 2
4. Will we see the Red Flag? No
5. First one to crash his car? Perez
6. How many cars will finish the race? 18

Aww, #91 Viper has a problem. Hiss.

I'm hoping the Viper can hold off that Ferrari assault, looks as if it's a matter of time, though.

I'm going to go with Ricciardo and Gutierrez dropping out in Q1, together with the obvious Cartinghams and Marusskias.

e: and two safety car periods in the race.

Last edited by NotAnIllusion, Fri, 15 Mar 2013 10:41.

1. Who will win drivers' world championship: Vettel
2. Which team will win constructors' world championship: RBR
3. Who will score more points in 2013. Bottas or Maldonado: Dolan
4. What is the best race finishing result for Adrian Sutil in 2013: 6th
5. Do you think Sergio Perez will win at least one race in 2013: No
6. Who will score more points in 2013. Hamilton or Rosberg: Hamilton
7. First driver you think will lose his drive during 2013 (miss at least one race): Bianchi
8. Will Caterham or Marussia score points in 2013: No
9. Do you think Massa will win at least one race in 2013? No
10. Does Kubica drive F1 car before the last race? Never
11: Winner of Australian gp: Vettel
12. Winner of Monaco gp: Alonso
13. How many points will the dwc winning driver have at the end of the season: 299

http://www.geek.com/articles/g ... railer-released-20130213/

GitS <3.

iRacing master 'race'

Last edited by NotAnIllusion, Wed, 27 Feb 2013 12:24.

Mokoma - Kasvot Kohti Itää
https://www.youtube.com/watch?v=ib_Yx0PSXeI

Quote from Mountaindewzilla :

your post is very condescending.

Touché.

Afaik one of the devs said that tyre wear is extremely minimal in this tech preview. Also, I read this http://www.racedepartment.com/ ... 5014/page-12#post-1376896. It's independent of FoV, which is nice. Setting FoV to 40, and then 'set driverEye.z 0' made it quite interesting.

AC should detect all connected devices, and then you can assign any detected button or axis regardless of device, so it should be fine.

Quote from Franky.S :

Radeon X1650 Series

is this too outdated? what would you reccomend for a low budget/good card?

It's outdated because it's a DirectX 9 card. The lowest AC supports is DirectX 10.1. Therefore, you need at least a "DX10 card", but it would be silly to get a non-11 one at this stage.

Not sure if it's been mentioned that it's possible to watch replay files by editing the file name into Documents\Assetto Corsa\cfg\race.ini. Add the file name and change active to 1. The replay will be loaded the next time you go to the track, at least in hotlap mode. It's not necessary to restart the launcher, only acs.exe.

Quote :

[REPLAY]
FILENAME=lotus_elise_sc_magione_22-2-2013-19-3-32
ACTIVE=1

I have an i5-3210m laptop with a 630m graphics card. At 1366x768 with pretty much everything turned way down, AC tells me that my average is usually between 71 and 75 FPS.

Quote from Töki (HUN) :

steering linearity option.

Documents\Assetto Corsa\cfg\controls.ini

[STEER]
SCALE=###

Well here is my crappy 1:25.182 with mouse and keyboard. https://www.youtube.com/watch?v=ciXuqJp_pqw&hd=1

All of them with mouse and keyboard. The only sim that I've used a wheel with is LFS. LFS feels quite different to GTL, GTR/2, PnG mod, iRacing, nKP, AC in my opinion.

Feels nothing like LFS, closer to a mix of iRacing and nKP.

So far:
- UI is nice, but lacking some options that are present in ini files (FoV, steering linearity).
- UI button animation is annoying for two reasons 1) there is a delay and 2) the position of the button changes from where it was when I hovered over it. Solution: remove delay, keep buttons where they initially are, keep some sort of animation.
- Lack of mouse steering option is puzzling. Keyboard controls are there, so it's not because 'too arcade', and nKP has supported mouse steering for a long time now.
- Got mouse steering and shifting to work with ppjoy+glovepie (as a wheel and pedals), steering linearity in the ini file seems to work.
- Says average FPS is 70-ish, I have everything turned off / minimum. i5-3210m and 630m. That's not too bad, but there are drops and 30 FPS is completely unplayable.
- What's with the automatic clutch??
- Please for the love of Pete add a 'lock UI' option for mousers (when mouse support is added). Currently it's *extremely* easy to accidentally open the menu, click something or drag something during normal steering and shifting operations.