Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
there's a new version by the same author
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=2688892244
Can't say that I've noticed the "weird reflection" in windshield and I only use inside cab view. Not saying the issue doesn't exist, I have haven't noticed it. :)
Do you have any of these problem?
I have tried that one all ready before you told me this.
What is the weird like reflection in the windshield.
Is this going to be fixed?
There are no air brakes. Is this going to be fixed to?
Before I buy the truck it again.
But besides that the truck drives nicely. I think your truck is the only ARI sleeper in the workshop. Very nice.
All the references to oculus are going to be vr-specific items that exist in the 1.4x[oculus] beta branch.
My assumption (not being a HUGE Blender guy, but grasping the basics) is that there would be two camera objects referenced in the .blend that gets exported to the .scs file.
* One interior camera for flat 1.42 monitor gameplay
(interior_camera: camera.interior.long)
That one being the one that you move (with animation controls and a path defined in blender, maybe?) from the driver's seat to the back of the long sleeper.
* A separate interior camera for the 1.42 [oculus] branch
(interior_camera_oculus: camera.interior.w900.oculus)
that has the same XYZ coordinates, but doesn't animate or move - it relies on the *headset* to move the viewpoint around that XYZ coordinate.
OR
Just the *REFERENCE* to the w900.oculus camera is enough for it to work. The client finds that object in the original W900 file and uses it without objection.
I could test the hypothesis, I guess, by changing the camera.interior.kenworth.w900.oculus line to match the one for the Mack - camera.interior.mack.anthem.oculus - and see if it moves the camera to the wrong place for the W900, but the same XYZ coordinate that you'd expect it to be for the Anthem.
interior_camera_oculus: camera.interior.kenworth.w900.oculus
to
interior_camera_oculus: camera.interior.kenworth.long.oculus
I have no clue as to what the oculus is or if its part of the w900 file or its an internal command with in scs
I mucked about with the .sii files in Notepad++, cloning and renaming some pieces from the w900.oculus cameras, totally hosed something up, force-quit ATS. Relaunched it on Desktop.
Unsubscribed -> Waited 2h (watched a movie with my Infinitely Better Half) -> Resubscribed
It now works flawlessly in VR.
I dragged my racing rig out to the middle of the room and I could even get up and walk around in the sleeper.
No idea what the problem is/was before resubbing. /grumpy
I just checked the data.sii file and my edit from earlier is still there.
interior_camera: camera.interior.long
interior_camera_oculus: camera.interior.kenworth.w900.oculus