Already having a problem just installing it.  I'm getting an error message that MSVP100.dll is missing.  I will attempt to rectify this problem tonight.

got it installed - can't open. had a similar error as you, Ed Cafarella, that a dynamic link library is missing. although not MSVP100. missing dll was pthreadVC2. When I re-unzipped to /Program Files (x86) that problem went away.  Now when I click to open \starrynight.exe I get the following error:

starrynight.exe - Entry Point Not Found

The procedure entry point

?id@$codecvt@DDH@std@@2V0locale@2@A could not be located in

the dynamic link library C:\Program Files (X86)\Starry Night\starrynight.exe

Hi Edward,

On Windows, if you get the MSVCR110.dll Error message it can be resolved by installing the following software

http://www.microsoft.com/en-us/download/details.aspx?id=30679#

32bit: VSU_4\vcredist_x64.exe
64bit: VSU_4\vcredist_x86.exe

Hi Keiron,
Registration number doesn't work

Installed no problem on Macbook running Mavericks

Installed on a Macbook Air and a Mac-mini, and I have to say that the graphics performance is very medicore compared to SN6. Are other people seeing the same problems?

A bit slow loading but seems fine once up and running on my Macbook Pro, it is an early 2011 2.3GHz model though is running a 512gb SSD and 16gb of Ram (yes I know Apple say it only takes 8!)

Just loaded the latest build. Activity monitor shows SN7 consuming 81-95% of CPU cycles. I've shutdown nearly all background tasks and reduced graphics settings but it hasn't made a significant difference.

Can I suggest that we need more forums than just the ones for telescope mounts?

I take it all back! After disabling all extensions and startups and booting clean, SN7 runs fine. There is obviously some interaction with some extension going on, so I will need to see if I can isolate it. Hopefully it's not something essential like Alfred.

Just loaded the latest version on my Mac Mini and it works very well without disabling anything, so it looks like the latest build has fixed something impacting graphics performance.

I have yet to get past the msvcr100 error when hitting program start icon.  I have downloaded several builds to no avail.  Operating system is win7 premium 64 bit.

I did look into the installed files and did not see where the msvcr100.dll even exists.  I downloaded both x86 abd 64 bit links as mentioned. Uninstalled, reinstalled.  Still no go.  I am currently downloading the 27 March beta version, hoping something works, I really would like to test this software out with the telescope.

Best Regards,

Jeff Turner

I am going to try unzipping to program files x86 as suggested in a comment above and see what happens.

I am attaching screenshot of the installed files from starry night pro plus 7.  Still no go the msvcp100 dll missing error still keeps coming up.  1 file attached screenshot.  I would think the msvcp dll file would be located in the installation directory.  Once again I have downloaded the Microsoft links and installed both files from links provided if this error comes up. 

Ok I have a resolution to anyone with windows who has the msvcp100 error and it continues. Search computer for the msvcp100.dll.  COpy and paste any mscvp 100 dll you find into the starry installation folder under programs x86/starry Night Pro Plus 7.

When I run exe at this point new error showed.  Cant run missing mscvr100.dll, so search computer for this file, where ever you find it copy and paste into same mentioned directory above.  Starry Night Pro Plus 7 now works.

Best Regards,

Jeff Turner

I have had time to sit down with program for about hour now.  I am getting lots of crashes when I zoom in on objects such as planets or dso's and try to choose any of the menu options from pop up menu for the object.  I am filling in all info the the automatic reports which are generated due to these failures.  The program seems to be crashing often just while bringing up objects within the planetarium program.  For reference my OS is win 7 64 bit premium edition.  Video card is the Nividia GTX 285 with 2 gigs of onboard memory.  I did end up turning off shaders in opengl.  Crashes are still happening quite often. 

I do like the look and feel of the new verison, feels like I can jump between program features quite rapidly compared to verison 6.4, even though I have only been using beta version for few minutes. 

Best Regards,

Jeff Turner

I am currently using mar27 beta build for above referenced comment.

I will say that the planetarium screen is way faster at responding to changes then version 6.4, nice improvement!

I will be installing the beta next on my observatory laptop computer and will be testing mount operations of my cgem with the beta software next few days, will send back reports and such, I know you have great interest in hearing from those who operate gear via the software.

Best Regards,

Jeff Turner

Sorry for all the posts at this location, just spotted the beta testing submit report link!

It would be helpful if there are release notes with each update. I don't know if a new update is supposed to deal with my scope connection issues or not.

I agree, John. It'd be nice to know what has been addressed since the last build.

It makes testing a very hit and miss affair. With each new update I have no idea what my testing should focus on. For instance, I have a scope control problem that has lasted for the last few updates. I have no idea if any of these updates were supposed to address my issue and the solution has failed, or if my issue has not been addressed. It makes it really hard to know what to look at.

I'm a professional software tester, and if I was presented with a release and no release notes at work, I would send it back as "failed testing due to lack of documentation".

It's getting a bit aggravating. I just got 7.0.0.93, and I've no idea what's been changed. Going through my list of potential problems to see which ones are still there is, at best, time consuming. For example, I've reported some problems with the orbit editor. The problems seem to still be there, but should they be? Should I bother checking?

It'd be useful to have a list of items on the developers' to-do list, with some indication of things they'd like to get checked out and items that can wait.

I initially had some issues which I thought were crashes and bugs when using the emphemerides generator, I have since found at I was making mistake of trying to generate these while zoomed in on object, if one does so it crashes program. To generate emphemerides one must not be zoomed in on the object, it will work fine.

I see few comments in this post where people not sure what to do for beta test.  From what I have read here the direction are listed above in this topic,  one must work down the check list for this topic, and submit results to listed forums for each step as indicated.  If one has telescope mount it looks like they want telescope owners to operate gear as much as possible with software and submit findings and crashes under appropriate indicated telescope. 

For all crash reports log in at http://beta.starrynight.com/  and submit report via this url.

Keiron,

When do you anticipate Starry Night Pro 7 Beta files will be available for testing?

Thanks

J. Turner

Downloaded and ran through the whole Beta checklist for Starry Night Pro 7.  No crashes, stable, did not have any issues.   OS is Win 64 bit premium edition.

Is there a Starry Night 7 Pro Plus version for Windows 10 yet?

Hi Mark,

Starry Night will run on Windows 10.  The issue may be driver compatibility.  Do you have a certified Windows 10 driver for your graphics card?  If so, go ahead and run Starry Night 7 (public or beta) and let me know what happens.  

Thanks!