FPS

[robbit]

Awesome thanks for the list FOV=85 looks good

[robbit]

In huge US engines is easy, the problem is tweak all at same time on SD40-2, SD-38, GP-7, GP-9, SW1200, SW1500, steams in general (holding firebox)...

But I was talking about the Class 67 not american

[maxsdad]

Doc:

Again, thanks for all your wisdom.

maxsdad

[Machinist]

Awesome thanks for the list FOV=85 looks good

Humm... looks like FOV in games works in the opposite way of lens diameter (FOV in photographic machines).
FOV=85 gives a wider view (very nice in cab) though objects are unrealistic farther. I'll try other settings and post them soon... Thanks for the info.

[robbit]

Yes I only tested in cab I tried 70 and 85 they both looked good

[robbit]

When you tried the command line for multicore did you try -Multi-core or -Multicore?

[robbit]

I think -Multi-Core works Please somebody test this and let me know

[Machinist]

MultiCore: average 15fps 65% processor usage
Multi-Core: 15fps 72% usage

Are you right?

About FOV samples see this other post:
viewtopic.php?f=6&t=5665&p=57478#p57477

Cheers,
Doc.

[peterhayes]

Doc
What about
-followaitrain ?
PeterH

[Machinist]

Doc
What about
-followaitrain ?
PeterH

Peter
That I don't know yet, but last night I tried one that is really ultimate and awesome, a dream for scenarios writers and users: -SmartAITrain (case sensitive, of course)... with that setting AI trains obbey red signals, signal blocks and never hit each other neither against your Player Train! But, well... Everything was going very well when the clock's alarm rang and I woke up. It happens... was so good to be real
Doc.

[peterhayes]

Doc
You haven't been at the Brazil nuts again?
pH

[robbit]

Wait! I thought he was the Brazil Nut. hmmm...

[peterhayes]

No!
Actually, he's an Off the Wall Nut!
pH