Hivatalos oldal I Hivatalos fórum I Steam I Magyar Steam csoport I Facebook oldal I Magyar FAQ I Setupok I
-
Screenracer #10676 Még jött egy kis javítás, meg miegyéb.
Build 999-1001 (03/05/15) - The last MBs
Render:
* Integration of DX11 ambient shadows bug fix
Build 998 (01/05/15) - This time the "ACTUAL" Last GBs
Render:
* Fix for GroundCover performance issues on NVIDIA GPUs
* Further optimisation of VB/IB sizes, to improve SLI performance.
* Change to how the special effect system fixes up headlights. WMD-6752
* Add NVIDIA Titan X to list of very high end cards (for first run settings).
* Predefined settings tweaks - change prerendered frames to 1 for high/very high configs
* PitsequenceController: Switch off automatic switch to CockpitCam when using Oculus Rift
* DX11: Fix for tracking issues with Geometry shader constant buffers (fixes performance / hack previously required)
API:
* WMD-6741: Added basic LED support (tilde through to backspace for revs) for Logitech gaming keyboard. : rob
* Shared Memory fixes: Added states "GAME_INGAME_RESTARTING", "GAME_INGAME_REPLAY", "GAME_FRONT_END_REPLAY". New mGameState states required. I've now added "GAME_INGAME_RESTARTING", "GAME_INGAME_REPLAY", "GAME_FRONT_END_REPLAY". mCurrentSector3Time always invalid, This now works identical to the HUD display. This also means now that mCurrentSector1Time & mCurrentSector2Time will display valid values, even when not in their sectors (as the display does). For the current current-sector-time... this can always be checked for app-side against the mCurrentSector attribute. The mCurrentLapDistance also increments at relatively coarse intervals of ca. 5m (is this normal?) [Resolved] Yes (well due to ease of access in-game!) This is due to the fact that the 'best waypoint' is being fetched, and they are placed approx 5m apart from each other... this is how the current lap distance is determined in much of the game-side code. That said, I've pulled a snipped of code from the physics which calculates the distance between the current waypoint, and the next best one, which now produces a linear result. When starting a new lap the current sector and current lap are not always synchronised. When starting a new lap the lap distance is sometimes still on the old lap [Resolved] I ran into the same issues with the lap distance overlaps in the achievements, in which I've pulled some code over from there which was use to sort that out.
Controllers:
* Fix for centre spring being active during driving.
* WMD-5727: Fanatec force mixing set to software to remedy steering jolt issues.
Dedicated Server:
* WMD-6658: Support for dedicated server gameplay stats and logging: Implemented protocol to send stats and events to DS. Added hooks to send multiplayer stats and events to DS all over the place (session setup and status, player status, various participant events including sector/lap times, results, impacts and cutting the track). Updated ping call to send the server RTT to DS, and fixed issue where pinging could break disconnection timeout if the server still responded to ping (which is allowed even when not in the session) but not to anything else. Bumped protocol version to 50
Utoljára szerkesztette: Screenracer, 2015.05.04. 11:01:45