[Solved] Game Freezes On Notebook

  • #1, by marchardSaturday, 19. August 2017, 18:58 3 years ago
    Hello,

    I'm using VS 4.2.5 and have been working on my game since a year now. It runs without problems on my Win7 development desktop pc both in the editor and as a build. Also on other test machines, which are a other Win7 desktop pc and a Win10 pc, it runs without errors.

    Now I tried it the first time on a notebook with a non dedicated video card. It is a Dell Latitude with Win7 and a i5 CPU with 8GB Ram and a Intel HD 4000 graphics. Due to the Visionaire minimum system requirements, it must have at least 512MB shared VRAM.

    The system settings on the notebook show, that the HD 4000 has 64MB dedicated memory and 1632MB shared memory. The game starts without problems in the editor and as well as build game.

    But if I click on certain objects in the game, or when certain text should show up, the game freezes. These bugs are reproducible, but I have no idea what causes them, because on all other test machines it runs well.

    Attached is the messages.log.

    18:07:56: Engine Version: 4.2.5 (Build 1185 from Build date: Nov 24 2015)
    18:07:56: Time needed for preloading game: 40 msec
    18:07:56: Initializing graphics interface. Surface size: 1280x720, render size: 1280x720
    18:07:56: Using Framebuffer with texture.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: log: No errors.
    18:07:56: red, green, blue, alpha, depth size: , doublebuffer , accelerated
    18:07:56: Serialization finished. Needed time: 102 ms
    18:07:56: SetupParents finished. Needed time: 2 ms
    18:07:56: SortLinks finished. Needed time: 0 ms
    18:07:56: Interfaces loaded. Needed time: 4 ms
    18:07:56: Scripts loaded. Needed time: 9 ms
    18:07:56: Time needed for loading game: 840 msec
    18:07:57: log: ERROR: 0:13: 'assign' :  l-value required "color" (can't modify a uniform)

    18:07:57: log: No errors.
    18:07:57: log: Attached fragment shader is not compiled.
    18:08:13: Error: can't open file '' (error 0: der Vorgang wurde erfolgreich beendet.)
    18:08:13: Error: Could not open file ''
    18:08:13: Error: Accessing buffer of memory file but buffer does not exist
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40


    Have the bugs something to do with the few dedicated video memory on the notebook, or is it something else?

    Would be great, if somebody could help me.

    Thanks,
    Marc

    Newbie

    40 Posts


  • #2, by SimonSSaturday, 19. August 2017, 20:54 3 years ago
    This is probably something else, please try it with version 5, but keep a backup of your ved.

    Thread Captain

    1368 Posts

  • #3, by MachtnixSaturday, 19. August 2017, 21:25 3 years ago
    Zwei Ideen, komplett ins Blaue gedacht:

    Vielleicht benutzt der Laptop-Grafikchip Bereiche des RAMs, die anderweitig belegt sind. Beim Zugriff von Visionaire auf diese Bereiche gibts den Kollaps.

    Sind alle User-Ordner, die Visionaire benutzt, tatsächlich freigegeben für den jeweiligen Benutzer und nicht schreibgeschützt?

    edit: Sorry, I didn't remark that the thread is in English...

    Thread Captain

    1087 Posts

  • #4, by marchardSunday, 20. August 2017, 11:30 3 years ago
    @SimonS @ Machtnix

    Thanks for your answers. I tried it with version 5 and the bugs are gone.

    I think 4.2.5 has major problems with OpenGL and the shared memory of onboard graphics cards like Intel HD 4000 series. DirectX works.

    But despite it, I will stick to 4.2.5 for now, because I had some smaller issues with VS 5, but they don't belong to this thread.

    Thanks

    Newbie

    40 Posts

Write post