Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Test build 2014-07-20
07-27-2014, 04:49 PM
Post: #16
RE: Test build 2014-07-20
Good luck!
Visit this user's website Find all posts by this user
Quote this message in a reply
07-27-2014, 05:58 PM (This post was last modified: 07-27-2014 06:10 PM by NaN.)
Post: #17
RE: Test build 2014-07-20
(07-27-2014 04:49 PM)GunChleoc Wrote: In order to view links, you must have to reply to this thread.Good luck!

Could you do a quick test with this executables, just to see if it still crashes: In order to view links, you must have to reply to this thread.

They are meant to be used with last test build (vdrift-win32-2014-07-20.7z).



Optionally, to get correct rendering you will also need to update data/shaders/gl3/deferred.conf :
In order to view links, you must have to reply to this thread.
Find all posts by this user
Quote this message in a reply
07-28-2014, 07:48 AM
Post: #18
RE: Test build 2014-07-20
vdrift_intel works fine, vdriftd_intel gives me an error


Attached File(s) Thumbnail(s)
   
Visit this user's website Find all posts by this user
Quote this message in a reply
07-28-2014, 12:57 PM
Post: #19
RE: Test build 2014-07-20
This is unrelated to vertex code. As long as it is not crashing the release build, it should be ok.

Did the log file ( C:\Users\<user>\AppData\Roaming\VDrift\log.txt ) contain any errors, except for the missing roads?

Something like: "ERROR: Framebuffer is not complete: ..."
Find all posts by this user
Quote this message in a reply
07-29-2014, 11:06 AM
Post: #20
RE: Test build 2014-07-20
I can't reproduce the crash, and the log file had been overwritten already.
Visit this user's website Find all posts by this user
Quote this message in a reply
07-29-2014, 11:22 AM (This post was last modified: 07-29-2014 11:23 AM by NaN.)
Post: #21
RE: Test build 2014-07-20
(07-29-2014 11:06 AM)GunChleoc Wrote: In order to view links, you must have to reply to this thread.I can't reproduce the crash, and the log file had been overwritten already.

Forgot about this one. After a crash the game will use failsafe settings. You have to delete C:\Users\<user>\AppData\Roaming\VDrift\VDrift.config to get the default settings back.
Find all posts by this user
Quote this message in a reply
07-30-2014, 06:07 AM
Post: #22
RE: Test build 2014-07-20
If I delete the conf file, the crash reappears. On second start, everything works again. Here's the log for he crash:

INFO: Starting VDrift: development-full, Revision: latest, O/S: Windows
INFO: Home directory: C:\Users\Beatrice
INFO: Settings file: C:\Users\Beatrice\AppData\Roaming\VDrift/VDrift.config (does not exist, will be created)
INFO: Data directory: data
INFO: Temporary directory: C:\Users\Beatrice\AppData\Roaming\VDrift/tmp
INFO: Log file: C:\Users\Beatrice\AppData\Roaming\VDrift/log.txt
ERROR: Failed to load C:\Users\Beatrice\AppData\Roaming\VDrift/VDrift.config
INFO: Disabling antialiasing
INFO: Disabling vertical synchronization.
INFO: Using GLEW 1.7.0
INFO: Video card information:
GL Vendor: Intel
GL Renderer: Intel® HD Graphics Family
GL Version: 3.0.0 - Build 8.15.10.2287
Texture units: 16
Maximum texture size: 4096

ERROR: Graphics card or driver does not support required GL_VERSION_3_3
ERROR: Initialization of GL3 failed.
INFO: Maximum anisotropy: 16
INFO: Maximum color attachments: 8
INFO: Maximum draw buffers (1 required): 8
INFO: Initialized render output: full_scene_depth (FBO)
INFO: Initialized render output: full_scene_color (FBO)
INFO: Initialized render output: normal_xy (FBO)
INFO: Initialized render output: material_properties (FBO)
INFO: Initialized render output: diffuse_albedo (FBO)
INFO: Renderer: data/shaders/gl2/deferred.conf
INFO: 0 joysticks found.
INFO: Loading car controls from: C:\Users\Beatrice\AppData\Roaming\VDrift/controls.config
INFO: Update status file C:\Users\Beatrice\AppData\Roaming\VDrift/updates.config will be created
INFO: Update status file C:\Users\Beatrice\AppData\Roaming\VDrift/updates.config will be created
INFO: Sound initialization information:
INFO: Obtained audio device:
Frequency: 44100
Format: 32784
Bits per sample: 16
Channels: 2
Silence: 0
Samples: 2048
Size: 8192
Sound initialization successful
INFO: Loaded fonts successfully
INFO: Loaded GUI successfully
ERROR: Framebuffer is not complete: incomplete draw buffer
Visit this user's website Find all posts by this user
Quote this message in a reply
07-30-2014, 09:22 AM (This post was last modified: 07-30-2014 09:23 AM by NaN.)
Post: #23
RE: Test build 2014-07-20
(07-30-2014 06:07 AM)GunChleoc Wrote: In order to view links, you must have to reply to this thread.If I delete the conf file, the crash reappears. On second start, everything works again. Here's the log for he crash:
The "incomplete draw buffer" looks like another Windows driver bug, as I don't see it happen on other hardware or under Linux. Luckily it is not critical, so that we can leave it as is I think.

Btw the Linux driver for Intel graphic cards seems to be much superior compared to Windows, performance and feature-wise.
Find all posts by this user
Quote this message in a reply
07-31-2014, 02:24 AM
Post: #24
RE: Test build 2014-07-20
I have a feature idea. Coloring the racing line.
So red where you should brake, green for acceleration, yellow for nothing. Maybe it's possible to get that info from AI and apply to vertex colors ?
Example from commercial game here (since 1:40): In order to view links, you must have to reply to this thread.
Visit this user's website Find all posts by this user
Quote this message in a reply
07-31-2014, 03:32 PM
Post: #25
RE: Test build 2014-07-20
(07-31-2014 02:24 AM)CrystalH Wrote: In order to view links, you must have to reply to this thread.I have a feature idea. Coloring the racing line.
So red where you should brake, green for acceleration, yellow for nothing. Maybe it's possible to get that info from AI and apply to vertex colors ?
Example from commercial game here (since 1:40): In order to view links, you must have to reply to this thread.

It is weird, but for some reason I have always found this feature kinda distracting when trying to figure out the braking/acceleration points. But then I would prefer a training drive with a leading car to learn the track instead of a racing line. So yeah... Big Grin

I see the additional value it provides though. I'll add it to the issue tracker. Thanks for the suggestion.
Find all posts by this user
Quote this message in a reply
08-02-2014, 02:00 PM
Post: #26
RE: Test build 2014-07-20
(07-30-2014 09:22 AM)NaN Wrote: In order to view links, you must have to reply to this thread.
(07-30-2014 06:07 AM)GunChleoc Wrote: In order to view links, you must have to reply to this thread.If I delete the conf file, the crash reappears. On second start, everything works again. Here's the log for he crash:
The "incomplete draw buffer" looks like another Windows driver bug, as I don't see it happen on other hardware or under Linux. Luckily it is not critical, so that we can leave it as is I think.
Sounds good to me Smile
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)