Jump to content

Sakru

Members
  • Posts

    99
  • Joined

  • Last visited

Posts posted by Sakru

  1. After of updating the LGE to version-4.2 Its start to crashing... and ill start the LGE from console in verbose mode to detect the bug that i "faced!!" so...

     

    The point is: when ill trying to click to a texture object in a assets panel to add some needed changes the LGE crash with this outputs:

     

    Segmentation fault

    Game removed: AppID 251810 "Leadwerks Game Engine", ProcID 11691

    No cached sticky mapping in ActivateActionSet.

     

    Any idea about it.. an how can i fix it?

     

     

    OS Debian Jessie8.6

     

    Are you trying to load Leadwerks directly from the Terminal? If yes, it will not run. You need to start Steam from a terminal and then open Leadwerks true steam to see a proper bug in Terminal window.

  2. That is what I use in the game that is currently in the game launcher. However that might be the reason the car becomes so glitchy when trying to load a new car level. That said the error above does seem like a bug. If not than there should be documentation on how to properly dispose of a vehicle/chassis.

     

    Setting vehicle to nil first and then releasing the chassis wont work.

     

    No bug in Linux, so this is Windows only. But game stops at second R hit.

  3. Hi guys. Tried to lunch leadwerks today, but it wont. After 10 second of loading Leadwerks logo, noting happens and leadwerks dies. Tried to lunch it from Terminal and i get this error:

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

     

    (Leadwerks:15385): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

    [s_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.

    [s_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

    root@sakru-desktop:/home/sakru/.local/share/Steam/steamapps/common/Leadwerks#

     

    I have Nvidia 1070, and i have tried to install different drivers with no luck. GTK-Warning is because of my theme, after installing standard Ubuntu theme, this bug has disappeared but this is continued to show up:

    <<<<

    [s_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.

    [s_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

    <<<<

  4. Okay. Thanks. I didn't know this before installing the 16.04 beta, so I can't run Leadwerks now with the open-source driver. But I've ahad n insane increase in performance in games like The Talos Principle, The Long Dark and Firewatch with that driver. Guess, I'll just have to wait.

    No worries. They didn’t drop support, they are working on new driver version for Linux systems, because catalyst never worked. New driver will be open source and, supported by AMD and community. I think it was to much for them to support buggy catalyst, so they decided to rewrite whole driver. First release will be out in the end of this summer i think... They just was not in time for 16.04 release date. Just stay on 15.10/14.04 until release of new driver. If you google, you will find more information on this.

    • Upvote 2
  5. Bugs are not distro specific, I'm running into same problems on Slackware. Engine works but there is still lot's of to do ...

    Maybe creator can focus more on fixing Linux bugs and bring Linux version more in line with Windows one, just saying.

    As i know, they will move Leadwerks from GTK to somthing else, question is what will it be... I mean, everybody who deployng software today, try to deploy it with QT but i dont know witch road leadwerks are going...

  6. But anyway, i do not want to tell that Leadwerks is bad and Josh doesn't doing his work. This project is proof that one guy can create this big project by himself. The only problem with that is, lack of support. Anyway, you are all right. What is the best for me is not always best for anyone else.

  7. I don't find many bugs in le and they ARE usually fixed quite quickly.

    Well, then i can tell you, that you dont know what are you talking about. All AMD users will never be able to play any Leadwerks game, because the bugs with shaders which i see on all platforms from Windows to Linux.. And noone is interested in fixing them. But everything working great in others projects. Same thing with Editor and functionality, on different platforms. For example on Linux. If you dont find many bugs, than maybe you are not working on the same level as i do.
  8. I would take Sakru's advice with a grain of salt personally. I wouldn't agree with that at all. That's like saying if you really want to drive a car you should make it yourself. You don't need to do that and in fact very few people are doing that in this day and age. You are just starting out, the idea is to start way smaller with your idea first and build the experience it takes to making a game. Seriously, your face game should only take a month and should be very very basic. Probably to the point where it's pretty boring but has basic game parts to it. GUI, player interaction with something, leaderboard maybe, very basic enemy AI.

    I never told anyone to do this my way... Car example is very bad. When you own a car, it is up to you how you want it to look, where to fix/do it yourself and so on. I like Leadwerks, but right now it dose not fit my needs. I have many bugs with it and i know that Josh will never fix them. They are on all levels, from Editor to Core. And i dont want to spend years by waiting Josh to fix them.

     

    What i tried to tell, it is up to you, if you want to learn API just do it. But in my opinion you will learn much more about how everything works and how to optimize or design when you doing it by yourself. And if i want to build a RTS game, why do i need to be worried about wrong design, which doesn't fit my RTS design????? I could make this list very long, and everything have to do with Leadwerks closed sourse.

  9. Mihaid, i can only tell you one thing. Game creation is like programming. You need to see the end result. I have my game on paper but i found that with all this game engines and tech on the market, it is very hard to succed. Just because the design is only sutible for large teams(from 5 to 50). If you would ask me, my answer is: without any understanding about how game engine, OpenGl/GLSL works you will never be able to make it to the end. I have buld my own rendering engine with all tech i need and i work on my own tools right now. You cannot even imagene how much you could do by yourself. I dont tell you that Leadwerks is bad. But i fell that the only way to learn and understand what you can do is to begin from scratch.

×
×
  • Create New...