You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

martyhr

Intermediate

  • "martyhr" started this thread

Posts: 384

Location: CZ

  • Send private message

1

Sunday, March 29th 2020, 11:56pm

Graphic context lost! Please reload......

Calling for help.
I get this error in krpanotools very often:

Graphic context lost!Please reload the page to continue....


Imposible to add some more hotspots.The tour has 25 multires panos ( equi 16.000x8.000).
Running on Win7(64bit), 24GB RAM and with free space on all HDD's more than 17GB.

2

Tuesday, March 31st 2020, 5:26pm

Hi,

what GPU do you have?

And is there an other GPU intensive application running at the same time?

Best regards,
Klaus

martyhr

Intermediate

  • "martyhr" started this thread

Posts: 384

Location: CZ

  • Send private message

3

Tuesday, March 31st 2020, 6:03pm

No other apps running.
Lenovo laptop with Quadro K2000M - 2GB DDR3.
I commented all pictures, video layers and even hotspots, but I had to finish the project manualy.
Find coordinates of resting hotspots by trial and error.

Never happened to me in the past. I work with 1.20.5.

Here is the result:http://devetsil.ghmp.cz/

4

Wednesday, April 1st 2020, 10:45am

Hi,

you could try using the 32bit version of the krpano Tools application.
That one uses a different NWJS/Chromium version as GUI framework, maybe that can help here...

Additionally or alternatively you could try manually setting a smaller memory setting
https://krpano.com/docu/xml/#memory

E.g.

Source code

1
<memory maxmem="400" devices="desktop" />


That might be able to help, but normally that shouldn't be necessary...
I think the core problem would be more between the NWJS framework and your GPU drivers...

Best regards,
Klaus

martyhr

Intermediate

  • "martyhr" started this thread

Posts: 384

Location: CZ

  • Send private message

5

Saturday, April 11th 2020, 9:31am

Thank you, Klaus. I'll try it.

noupunt

Trainee

Posts: 44

Location: Barcelona

Occupation: Photographer and programmer

  • Send private message

6

Friday, October 30th 2020, 7:14pm

It happens to me (and other users) some times... @martyhr could you solve it changing to 32 bits? and @klaus.krpano , is there any place where could we know on with device this issue will ocur? and also is there any effective diference between 32 and 64 versions?
Is happening in the 20 version. We are makeing a videoconference integrated tour so that is a big problem for us...

Thanks so much!

7

Sunday, January 10th 2021, 8:55pm

We are also facing same issue when we have large tours (140mb).

8

Friday, January 15th 2021, 12:19pm

Hi, try these things:
- updating the GPU drivers (manually)
- reducing the memory.maxmem setting
- check if you are using large single-res panos/videos or hotspot images in your tour

9

Monday, October 24th 2022, 12:41pm

Hi guys,
Seems like another few clues found.
Console log warnings constantly appears when running on ubuntu 22.04, FireFox 106.0.1 (64-bit) during VirtualTour browsing.

Some times scene's images falls down to black with:

Quoted

Graphic context lost!

But skin is still on screen)

Warnings from console:

Source code

1
2
3
4
5
6
7
8
9
10
11
tour.js:5:1714
WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER.

tour.js:5:1875
WebGL context was lost.

tour.js line 10 > eval:1:46843
WebGL context was lost.

tour.js line 10 > eval line 1 > Function:3:184
Use of the motion sensor is deprecated.

krPano console:

Source code

1
2
INFO: krpano 1.20.11 (build 2022-03-07)
INFO: HTML5/Desktop - Firefox 106.0 - WebGL

Source code

1
2
INFO: krpano 1.20.11 (build 2022-03-07)
INFO: Android 11 (SAMSUNG SM-G973U) - Chrome 87.0 - WebGL


Have this black screen stuff on some Oppo phone as well. But can't trace | provide the console warning yet.

Any ideas please?

10

Saturday, February 4th 2023, 12:46pm

The viewer also encountered the same problem. Will the next version fix it?