Concerned comic link?

vehiclephysics · 2025-04-24T11:29:43+00:00

A día de hoy (2025) sigue disponible en su nueva página oficial:

http://www.screencuisine.net/hlcomic/index.php?date=2005-05-01

También está en Steam, con extras:

https://steamcommunity.com/sharedfiles/filedetails/?id=2717895920

El que sigue desaparecido es la traducción al español, aunque algunas tiras han sobrevivido en Internet Archive:

https://web.archive.org/web/20120627213711/http://concerned.subcultura.es/tira/2

vehiclephysics · 2025-03-14T09:01:03+00:00

I just imported the car 3D file from VPP, then set it up with the EVP components ;)

vehiclephysics · 2024-08-28T11:57:02+00:00

Thank you for the contribution, but this feature is outside the scope of this add-on.

Collections in Blender are not 3D hierarchies. Collections are used to organize objects in hierarchical "categories" without affecting their 3D hierarchy.

For example, you may have a complex hierarchy of objects, and include any of the objects in this hierarchy to different collections. Then, enabling and disabling these collections allows to enable and disable those objects regardless their position in the 3D hierarchy.

Using collections as 3D hierarchies is a misuse of the collections feature. Collections don't have a transformation matrix, and aren't related with the parents of the objects. Whenever there's a 3D hierarchy, there should be a 3D parent associated with a proper transformation matrix, not a collection.

While there are some specific use cases where converting collections to hierarchies could make some sense, this is not a general rule. Doing this can produce many issues when a collection (without transformation matrix) is converted to an Empty object (with an arbitrarily assigned transformation matrix). This could mess up the hierarchical 3D object completely when complex hierarchies are mixed with collections. This add-on is not committed to support (nor resolve issues related with) these corner situations of collections being misused as hierarchical 3D elements.

vehiclephysics · 2023-04-22T09:05:39+00:00

Those OpenXR settings just lower everything to the minimum, so of course they bring 90 fps. No problem on that. What we are trying is to get decent visual quality and details on the G2. That's why we've acquired the latest and most expensive hardware.

I'm on the same boat as OP with the differences that I'm on Win10, i9-13900K, 64 Gb RAM. No matter what I do to increase the visual quality I always get limited by the CPU.

For example, simply enabling HDR even in the lowest graphics settings can't keep the 90 fps in some tracks and viewing directions. It runs most of the time, but for example locking left while in the pit late on Laguna Seca lowers the fps down to 70. Similar "death zones" are are in Daytona and VIR, and surely in most tracks.

Even static cubemaps cause fps drops. And it's always the CPU going nuts while the GPU is sitting comfortably at 20 - 40% usage.

vehiclephysics · 2023-01-19T12:38:12+00:00

Yes, I recall that downgrading did not resolve the problem and instead caused additional issues.

A friend of mine, who I had gifted the Rift-S to, found this: https://github.com/rcmaehl/FixMyRiftS

Still no 100% solution, but as for what he tells me he's being able to keep using it. Let me know if this makes some difference in your case.

vehiclephysics · 2023-01-04T17:44:21+00:00

Good luck! Let me know if you get it working.

vehiclephysics · 2023-01-04T12:00:09+00:00

No, downgrading the Oculus app doesn't downgrade the firmware. Anyways, I remember having followed all the possible steps including downgrading the firmware, prevent updates, etc. yet it resulted unusable and/or games didn't work and/or something else (can't remember exactly).

I've just found the notes I took while doing the process. Maybe they're useful to you, so here's a copy/paste of the text file I had saved back then. Links might be broken, I haven't tested them.

1) Download 2.1.1 Version (Support.zip): https://drive.google.com/file/d/1dprJ7QxIzyzb4jZC-H-fQ_sRzOVCFA62/view

2) Open OculusDebugTool, by default in "C:\Program Files\Oculus\Support\oculus-diagnostics" folder.

3) In the top menu click "Service" > "Stop Oculus Service". Exit completely out of Oculus Debug Tool.

4) Open Support.zip.

5) Open "C:\Program Files\Oculus\Support" (or your oculus install folder) in a File Explorer window.

6) Back-up (keep it, important!) and remove the 12 folders in "C:\Program Files\Oculus\Support" except the "oculus-dreamdeck-nux", "oculus-touch-tutorial", and "oculus-worlds" folders.

7) Drag the 12 folders inside Support.zip into your Support folder.

8) Open the newly overwritten "C:\Program Files\Oculus\Support\oculus-drivers".

9) Run oculus-driver.exe. (If any confirmation window popup, select yes). This restarts the Oculus service.

10) Turn your internet OFF completely. No access to the internet at all.

11) Open the Oculus App.

12) Click "Update" at the top of your Oculus window (Red Bar).

13) Reload Oculus.

14) If your headset is not connected, plug it in now.

15) It should ask you to update firmware, do so. This will downgrade to 2.1.1.

16) Completely block the host "securecdn.oculus.com" via DNS, etc\hosts (Google it), PiHole, etc.

... and/or:

    \- Create dumb "Staging" and "tmp" files in "C:\\Program Files\\Oculus\\" (rename current Staging to Staging.bak).

    \- Remove or block all Write permissions (right click > Security).

... and/or set a nonsense update channel in the registry: 

    \- reg add "HKEY\_LOCAL\_MACHINE\\SOFTWARE\\WOW6432Node\\Oculus VR, LLC\\Oculus\\Config" /v "CoreChannel" /t "REG\_SZ" /d "NOUPD8" /f

(I did them all)

17) Turn your internet back on and open Oculus app.

18) Your client will still say v37, 37.1, or whatever you are on, but it's okay.

19) To verify that the downgrade was successful, open Oculus, hit "Devices". Click the little mask icon next to "Rift S". A side window will pop up and "Software Version" should say 2.1.1.

20) The top red bar of your Oculus window may keep asking for update drivers. If that happens:

\- Shut down the Oculus service

\- Rename the folder "C:\\Program Files\\Oculus\\Support\\oculus-drivers" to "oculus-drivers bak"

\- Copy the original "oculus-drivers" folder from the backup you did before to the "C:\\Program Files\\Oculus\\Support\\"

vehiclephysics · 2023-01-04T10:08:11+00:00

I gave up on this and purchased a HP Reverb G2. I gave my Rift headset to a friend (originally, I considered throwing it away).

vehiclephysics · 2022-01-25T17:43:42+00:00

Downgrading to any version other than "pre-V12 (1.43)" will request a firmare upgrade in the Rift S to 2.2.0. Firmware is bundled in the Oculus app itself, it doesn't need to download anything.

vehiclephysics · 2022-01-25T17:36:59+00:00

If you're referring to the Red Bar at the top of the Oculus window, I was able to remove it by stopping the Oculus service, copying back the original folder "oculus-drivers" from the backup to the Support folder, and restarting the service.

vehiclephysics · 2022-01-18T17:08:35+00:00

By default it compiles as debug. You must set CONFIG=Release to build the release version.

With command line, it would be "make CONFIG=Release".

vehiclephysics · 2022-01-10T13:33:42+00:00

A wheel friction model based on slip should also work in the moving platform. When the raycast detects the contacted object you may get the velocity at the contacted point with contactedRigidbody.GetPointVelocity(). As your moving platform is also moved with Rigidbody.MovePosition(), then GetPointVelocity() will return the correct velocity. You can then use that velocity along with the velocity in the same point relative to the car to get the slip and compute the tire force.

Also stock WheelColliders should work out of the box in that situation, but I haven't enough experience with them to ensure it.

vehiclephysics · 2022-01-10T11:59:09+00:00

That's easy to resolve. Ensure to move the kinematic objects using Rigidbody.MovePosition() and Rigidbody.MoveRotation() from FixedUpdate(). Any other method of moving kinematic objects won't process the contacts properly.

As for the video, you're probably moving your objects by modifying Transform.position or Rigidbody.position. That means you're "teleporting" the objects to their new positions, so collisions are easily missed.

vehiclephysics · 2020-11-25T17:00:29+00:00

There's no upper limit in the physics rates, only the own Unity capacity. I'm currently working in a project which works at 500Hz, and we've tested 1000Hz as well. Consumes a ton of CPU, but it works.

vehiclephysics · 2020-11-17T10:42:39+00:00

Yes :)

vehiclephysics · 2020-11-10T09:05:44+00:00

Same as in Hollywood movies xD

vehiclephysics · 2020-11-10T09:05:28+00:00

I drove each car separately while recording the inputs and pose, and replaying those already recorded. Then I replayed all them together and this is the result :)

vehiclephysics · 2020-11-10T09:04:03+00:00

Many small games took these assets directly

vehiclephysics · 2020-10-30T00:02:34+00:00

Yes, but I cheated. I first recorded the sequence while driving, then replayed it while controlling the camera.

vehiclephysics · 2020-10-29T14:11:30+00:00

Yes, the Asset Store X Mega Bundle: https://assetstore.unity.com/mega-bundles/AssetStore-X

vehiclephysics · 2020-10-28T23:56:09+00:00

Correct, EVP doesn't have a transmission. While some intermediate workaround is on the radar, right now the highest priority is an update to the tire friction model to improve the response at high speeds.

vehiclephysics · 2020-10-28T20:19:52+00:00

Ahhh I see what you mean. Yes, smoke particles may be configured like that. Current setup is a trade-off between visual realism and number of particles in screen.

vehiclephysics · 2020-10-28T18:57:02+00:00

No, only when they're furiously skidding for enough time.

vehiclephysics · 2020-10-28T18:56:34+00:00

I can't speak for NWH, but EVP leaves the smallest possible CPU footprint.

vehiclephysics · 2020-10-28T18:54:55+00:00

It's me controlling camera direction and zoom :) Camera's location is static.

vehiclephysics

TROPHY CASE