RAM memory crash

This thread is a few years old. Some details may refer to an earlier version of Visionaire Studio. Current tutorials

1. Wednesday, 27. August 2014, 15:38 · 13 years ago#1

   excuse my english,
   
   hello, sorry for my first post I choose a crash...As I I have to say that this software is really good !
   
   But, while installed on my pc desktop everything seems to be ok, I had trouble on one of my laptops:
   
   
   --->When mooving an image objet ( the rock provide from the demo, first scene ) to place it on the scene ( first scene ) , the ram use is bumping to the max, and cause a crash.
   
   The project is very simple, I only use the recommended start minimum, and then set the way and walk area, place the rock, and it crashed very hard....It happened a lot of time.
   -My laptop is a pretty new clevo, with 16go ram, windows 7, GT650m.
   
   
2. × Working on a game?

   The free version covers up to 25 scenes per project. For more scenes and to sell your game, you need a license. Forum readers get the Indie Bundle 15 % off with the code FORUM15: €84.15 instead of €99, valid until 31 Dec 2026.

   Get 15 % off Try it for free
3. Wednesday, 27. August 2014, 16:06 · 13 years ago#2

   Hi, does the player work correctly or is this an issue of both editor and player ?
4. Wednesday, 27. August 2014, 16:18 · 13 years ago#3

   Hello,
   
   no it appear on the editor. If I run the player at the begining, everything is fine. I could'nt run the player after the ram bump of course ( after placing the rock ) , as it freeze than crash.
   
   EDIT : in fact it crash when using the program...
5. Tuesday, 31. March 2015, 12:38 · 12 years ago#4

   Hallo,
   
   erst einmal ein Lob für das Programm! Ich bin schon eine ganze Weile dabei, mit VS ein Spiel zu erstellen und schnüffele hier regelmäßig im Forum und habe schon viele Tipps bekommen.
   
   Nun habe ich aber ein Problem, was sich mit der Schilderung von oben zu decken scheint: Ich kann im Editor soweit alles machen und der Player macht auch keine Probleme. Sobald ich aber in einer Kulisse oder einem Menü ein Objekt erstelle und dem Objekt unter dem Reiter "Bild" ein Bild zufügen möchte schreibt mir VS den Ram voll (12GB), gleichzeitig treibt der System-Kernel meine SSD auf 100% Festplattenaktivität. Ich habe nebenbei das Logfile laufen lassen und das Problem scheint zu sein, dass, sobald ich in den Reiter "Bild" wechsle, entstehen hundertfach die Einträge
   
   Using Framebuffer with texture
   
   Ich vermute hier das Problem. Ich benutze WIN 8.1 64Bit mit einer GeForce 840m...
   Gibt es eine Lösung dafür? So ist an effektives Arbeiten leider nicht zu denken...
   Ich hoffe, Ihr könnt mir weiterhelfen!?
   Vielen Dank!
   
   Abstract in English ( is not so good, sry )
   If i want to edit the picture of an object from a menu or scene my system runs out of RAM (12GB) and my SSD works in short time near 100%. The process seems to be the NT-Kernel. In the same time the VS - Logile prints hundreds prints
   
   Using Framebuffer with texture
   
   I think thats the problem. My system is a WIN 8.1x64 with an Nvidia GeForce 840m.
   I hope you have a hint to solve this problem?
   Thank you!

   • 
6. Thursday, 02. April 2015, 23:44 · 12 years ago#5

   The problem is solved - without any help from developers...
   The secret is: create the object 1st at all at the left bar under the task objects and give it all features (like pic, actions etc..)
   AND then make the rest at scenery/menu - screen.
   Its´s strange but repeatable (on my system)!
   
   p.s.: the lifetime of my SSD increased rapidly...
   p.p.s: when game is ready for dispatch i will provide it here...
   p.p.p.s : this forum is great! THANK YOU ALL!!!!
7. Friday, 03. April 2015, 00:11 · 12 years ago#6

   The issue you are referring to is usually graphic card related. Did you try updating your gpu / cpu drivers etc?
   
   P.S: Sorry, but I didn't see the thread mentioned in the recent thread list.
8. Friday, 03. April 2015, 00:17 · 12 years ago#7

   “

   The issue you are referring to is usually graphic card related. Did you try updating your gpu / cpu drivers etc?
   
   P.S: Sorry, but I didn't see the thread mentioned in the recent thread list.

   „

   
   Yes, more up to date is not possible... ;-)
   Edit: I have the newest driver of IGP, chipset, GPU, OS and VS...
9. Friday, 03. April 2015, 01:11 · 12 years ago#8

   Hmm sorry. Often it's the drivers, but it seems a few people have had similar issues. Not sure why.
10. Friday, 03. April 2015, 01:19 · 12 years ago#9

    Perhaps i know where the problem is: what is VS coded in? C++ or sth. like that?
11. Friday, 03. April 2015, 02:26 · 12 years ago#10

    c++ for the most part.
12. Friday, 03. April 2015, 11:29 · 12 years ago#11

    Was that issue only reported by Nvidia-users? I daresay thats a bug in Nvidia-driver which is caused in OpenGL ( i think VS uses this, right? ). I saw similar loops years ago.
    But unimportant - i solved the problem for me. :-)
    Thank you!