Page 16 of 113

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 19 Mar 2017 13:27
by Gnargenox
Huh? No HiRES photos to change into textures of the topography? No mod to stick in my folders? I could have sworn I've seen other's pictures somewhere of the Valles Marineria with spaceships flying by. Is the same true for all the planets in the solar system? I'm almost afraid to check out the moon or Venus now...

Oh ok, Well I'm pretty sure I will do what ever it takes to add higher resolution pictures to the folders. Any pointers on where to learn about that?

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 19 Mar 2017 13:33
by Xoran
I could have sworn I've seen other's pictures somewhere of the Valles Marineria with spaceships flying by.
There is Solar system HD and Solar system Ultra addons in the download page, which increases resolution on blurry Solar System bodies. :)

Note that Solar system Ultra doesn't work without Solar system HD!

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 19 Mar 2017 13:38
by Gnargenox
AWESOME! Thank you kind sir!

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 21 Mar 2017 13:48
by VoyagerX
yeah but yet their terrains bumpiness and definition will not be the same as procedural planets.. may i be wrong?

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 21 Mar 2017 16:02
by Mosfet
VoyagerX, no, you are right. For now, that's the price to pay in order have accurate depictions of real bodies. In future this could change, though.

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 21 Mar 2017 19:30
by Hornblower
Erm, Is the second name for this star supposed to be weird like this?
scr00214.jpg
scr00214.jpg (68.29 KiB) Viewed 5059 times

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 21 Mar 2017 20:20
by Mosfet
Hornblower, no, it should be BD+22 1807.
It was mentioned in the old forum too, probably it was missed.
Script is:
Remove "U Gem/BD +22°1807/AAVSO 0749+22"

StarBarycenter    "U Gem/BD+22 1807/HD 64511/AAVSO 0749+22"
{
    Class    "DA"
    RA        07 55 05.24
    Dec       22 00 05.1
    Dist      82
    AbsMagn   9.5
}
to be placed under Addons\catalogs\stars\
or a .pak can be placed under Addons

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 22 Mar 2017 19:43
by Hornblower
Another thing, real planet brightness doesn't seem to affect other stars in the system. For example, a Y class brown dwarf should be just a dark as a planet orbiting it, but this is not the case. (Can't tell if this is a bug or a limitation)

Exposure is turned up here:
scr00223.jpg

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 23 Mar 2017 14:03
by planetariumguy
First off let me say that this program is awesome. I use it educationally to teach children about the universe and they love it. So thank you for all your work.

That said, I have found a bug with the controls where all the joystick buttons I program get wiped if I do the following.
  - start space engine without joystick
  - shut down space engine
  - plug in joystick
  - start space engine with joystick

Is there a way to keep the joystick control settings from resetting when I use SE without said joystick? 

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 24 Mar 2017 05:24
by Gnargenox
Yesterday I updated my video drivers. I'm not sure if that plays any roll in my most recent problem. I have not noticed before that when starting time to progress, I fly off the planet I have landed on. I do see that when this happens I am set to "Following" rather than "Rotating". Also when I start the time, speed is fairly low, less than x300. Am I missing some setting I might have changed elsewhere? How could this be related to a video driver update? I am fairly confident this has not happened before, the planet flying away from under my feet. TY

I should clarify that I dont understand how I came to be Following after landing on the planet. I forget what the distance is, and I realize at some height above the surface I automatically change from Rotating to Following, but usually just moving around with the SWAD keys and a little 1 or 0 to get over a mountain has not affected that setting.

(I use a GeForce GT730)

Update: Definitely a display issue is the culprit here. Objects blink out of view when overloading my video memory, If I collide with a mountain it will re-render, disappearing momentarily switching my mode to Following while it is gone and reverting back to Rotating when it reappears. If time is moving I will be following the length of time the object under my feet is not shown, and will not return to Rotating since I will have traveled too far. I guess I better roll back my drivers. I hate updating software more than most things in life.

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 24 Mar 2017 08:24
by Mosfet
I tried to replicate the issue from your description but I couldn't.
Something similar happens when I reset time, which is normal, but not by resuming it.
Is your camera in free mode?

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 24 Mar 2017 13:05
by Gnargenox
Yes, typically it is. The first time this happened though I was in Aircraft mode and was about to start a video. I usually allow time to progress so the clouds move etc. I will position myself or load a saved location and be in Free mode, open the video recording window, hit 3 to go into Aircraft, press F9 to start recording and space-bar to start time and it is at that moment the planet falls away from under me leaving me drifting in space. I am sure it will be hard to replicate if you are not using the same system setup as I am. I'm pushing the limits with using only 2GB memory on the computer and 1GB on the video card. Last night I found an issue with my video card drivers and all is working much better now, with no re-rendering of the planet surface if perhaps too many stars become visible.

On a side note, in the past also, an eclipse of a moon will completely cover it so that it is fully in shadow. It becomes invisible for that moment and stars behind it show up. Once it is out of New Moon phase and any sliver of it is showing, the remainder stays solid and dark without seeing things behind it. Just a limitation of my video card I suppose.

Thanks

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 25 Mar 2017 03:29
by Xoran
Another thing, real planet brightness doesn't seem to affect other stars in the system. For example, a Y class brown dwarf should be just a dark as a planet orbiting it, but this is not the case. (Can't tell if this is a bug or a limitation)
A brown dwarf is categorized as a star, and as far as i know real planet brightness doesn't affect stars. :)
On a side note, in the past also, an eclipse of a moon will completely cover it so that it is fully in shadow. It becomes invisible for that moment and stars behind it show up. Once it is out of New Moon phase and any sliver of it is showing, the remainder stays solid and dark without seeing things behind it.
Could you please attach your se.log file, located in the system section of the SpaceEngine folder? You use Add files button, the same button you use to attach images on our computer. ;)

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 25 Mar 2017 12:31
by Gnargenox
As soon as it happens again I will

Troubleshooting and bug reports - SpaceEngine 0.9.8.0

Posted: 25 Mar 2017 14:22
by A-L-E-X
I have one and I was looking to upgrade what I have but I saw my motherboard does not work with any video card above PCI-e 2.0

Right now I have a Core 2 Quad Q6600, 2 GB DDR2-667 memory, 640 MB Geforce 8800 GTS 112 SP graphics card.  I set my computer to allocate 2 GB for video memory (640 MB from the video card and the rest from RAM.)  I am using XP Home x32 which does not use much RAM so I allocated most of my RAM for SE.  I run SE in a 1024x768 window so that should hopefully minimize its video memory usage

2 GB RAM is the most this motherboard will allow, however there is a bios hack that will allow it to take up to 4 GB RAM (but only 3.3 GB will be usable, even if I install a 64 bit OS.)

The two upgrades I am considering are:

https://www.newegg.com/Product/Product. ... -_-Product

EVGA GeForce GT 730 DirectX 12 04G-P3-2739-KR 4GB 128-Bit DDR3 PCI Express 2.0 Video Card

4GB 128-Bit DDR3

Core Clock 700 MHz

2 x DVI-I 1 x mini HDMI

PCI Express 2.0

I want the dual DVI ports since I run two monitors.

The other upgrade is

https://www.newegg.com/Product/Product. ... -_-Product

Crucial 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 667 (PC2 5300) Dual Channel Kit Desktop Memory Model CT2KIT25664AA667

DDR2 667 (PC2 5300)
Cas Latency 5
Voltage 1.8V

Should I do one or both upgrades, considering I will be limited by the motherboard to 3.3 GB RAM even if I go from 2 GB to 4 GB?  Also should I do the upgrade from the 640 MB graphics card to the 4 GB graphics card even though the 4 GB graphics card is slower?  See this:

http://www.tomshardware.com/reviews/gpu ... ,4388.html

On this hierarchy chart, it's 3 levels below my current graphics card, and my current card isn't the standard one, it's the SSC version with 112 shader processors, instead of 96, and performs more like an 8800 GTX (5 levels above the 4 GB card.)  Problem is this motherboard is a PCI-e 4x board so the graphics slot might be the bottleneck anyway and the motherboard doesn't support anything higher than PCI-e 2.0  I am considering the two upgrades though because they are relatively inexpensive and I already bought a 2 GB hard drive and a copy of Windows 10 32bit/64bit Home.  I'm not having any issues running the program in a 1024x768 window, however the program hangs upon closing and I have to kill the process in the task manager to close it (or tell Windows to close it in the pop up window.)  I also worry that future editions of SE will have higher requirements- is there any news about that or will the current requirements to run SE hold for foreseeable future versions?  I noticed that the video memory and RAM requirements have gotten higher with more recent versions.  The other thing is I noticed via EVGA Precision that SE uses over 95% of my graphics card, is that dangerous to the long term health of the card and will it shorten its life?  Would that be just as bad with the new card, should I get it?