Hi,I too have been wanting to purchase ActiveSky but from what I've been reading in these threads, its been a disaster. Perhaps it was released to early? Just curious. Having used the old ActiveSky I'm confident Damian will correct the problems. The purpose of my post is to find out whether HiFi believes the problems will be corrected soon or if they'll have to wait til MS releases the weather SDK. I currently have FSMeteo and I know a lot of what people are expressing here are also prevalent in FSMeteo. The stutters during weather changing and sharp wind shifts for example are also prevalent in FSMeteo. Would like some input before making the purchase. Thanks.

DISASTER???? How in the world are you coming up with a "disaster" here??? As in any new program there are a few bugs to be worked out, but if you can find anyone more dedicated to getting things fixed ASAP than Damian and his crew, I'd like to meet him/her. Am I having issues? Yup, but until I've exhausted the manual and are certain that it is related to AS2, I'll keep on truckin with it. But this is anything but a "disaster" my friend. If you want to wait until you see fewer bug reports, then by all means, but as most of us are finding out, it is more a lack of familiarity with the program that is causing problems than the program itself. That too is normal, and will be worked out soon. So far, I'm extremely pleased, and I have no worries that whatever issues are at hand will be addressed in short order.

No "disaster" here. Seems to be working as advertised for me. About 5 hours total time so far in differing conditions and so far so good. Took a bit of tweaking to get rid of the sudden weather changes, but other than a problem with some severe wind shifts/speed changes (still tweaking, it's in there somewhere) I'm happy with AS2004 so far.Jim

>I've been reading in these threads, its been a disaster.Are you trying to redefine the meaning of "disaster" ? Some folks claim the operation "Iraqi freedom" has been a disaster. *:-*Michael J.

http://forums.avsim.net/dcboard.php?az=sho..._id=5809&page=3http://forums.avsim.net/dcboard.php?az=sho...g_id=5999&page=http://forums.avsim.net/dcboard.php?az=sho...g_id=5995&page=Hope this helps,JimActiveSky Support

I will be polite and suggest you get a dictionary and look up disaster. I see the normal fleshing out after a major release. The product is working fine for me which suggests that some people might have other problems.Disaster? Not even close.That's about as nice as I can be. Out of respect for Damian and the Beta Crew I will refrain from saying what I really think about the comment.Nuff said.It's a great program, you will not do wrong by purchasing it - PERIOD!Just MHO,Vic

Hi Jim,Yeah, I have to start tweaking shortly, but this is really (another!) great program Damian has come up with! I know this is a royal pain in the backside, but would you be willing to post your tweaks to date here somewhere so I can compare notes and maybe save a bit of time? I'll understand if you can't, but it might save a lot of "reinventing the wheel" stuff here for a number of us.Thank you Jim. Appreciate whatever you can do for us.

Thanks to everyone for your support!JimActiveSky Support

Check at the bottom of this thread in this forum:http://forums.avsim.net/dcboard.php?az=sho...g_id=5836&page=Larger issue would be system specs. Mine are at the bottom of my message.Jim

Ahh yes, I did see this earlier Jim, and didn't clue in. Thanks VERY much for this! Appreciate your time.

Not a problem, e-mail me direct if I can help. Not always in the forums, but staying on top of what other people are doing with AS2004 today.Biggest key so far has been making sure the local suppression range (AS2004) and cloud draw distance (FS9) are the same and that the distance can keep up with your aircraft moving through reporting areas. In the DC-3, 50nm is probably overkill, but in a 737 it is just about right. Going to mess with that a bit more and see if I can get any improvements, as it periodically will still jump, but I think that is due to having global writes on and being in an area with not a lot of reporting stations.Jim

Disaster is a strong word, true enough. Let's say this without very much hesitation: the software was not ready for prime time. With time, patience and TLC perhaps it will be.Having succeeded getting a flight plan loaded into Active Radar, I went about pushing back. Now the keyboard is locked up tight: no pushback, no function-key flaps, no 'G' for gear and no keyboard view changes. Spare me the trivial suggestions - it remained plugged in alright! In fact, the keyboard worked just fine typing this, worked fine in the FSNav window and even allowed me to get there with F9 - just not within the FS9 window - or in any view. Every trick I could think of failed to recover the keyboard. This has never happened before and doesn't now unless Active Sky is up and limping.Another curiosity: the mouse scroll wheel (USB) quits working - in things like the autopilot altitude-lock or heading gauges, or the altimeter's barometric pressure knob - if an Active Radar window has been opened. Unlike the keyboard I can bring the scroll wheel back to life by left CLICKING the mouse in one of these same areas. This problem will also disappear when the ActiveRadar window is closed again.And the piece de resistance: FS9 locks during termination, even when Active Sky was terminated first. None of these things has ever happened before my first evening of entertainment watching Active Sky struggle. I really haven't had a real good look at the weather yet... When is 1.1 coming out? Please? This baby's got to go back on the shelf 'til then!Norm

Hi Norm,Sorry you are having troubles. Based on the similar reports like this so far, I think the problem is one of the following:1) You have ActiveCamera, and have it set to CTRL-12, which is conflicting with the ActiveRadar module. Solution is to change ActiveCamera's hotkey. I am also working on enhancements to support changing the key in ActiveRadar.2) You had WC2 installed, and this is conflicting with the module installation. The WC2 warning was unfortunately omitted from the manual, my fault. Of course this will be corrected ASAP.Please let me know if this helps you. I think the vast majority of users so far have had little to no problems, these sorts of things can slip by beta testing (or be caused by last minute installation packaging isses), of course we will correct them as soon as possible. I think however the vast majority of issues WERE found by the beta team before release, I think they did a fantastic job at we actually have done quite well with this 1.0 release. Hopefully we'll get your problem sorted out right away and you can begin using the program :) Please advise if the above helps. Thanks!Damian ClarkHiFi Simulation SoftwareDeveloper of ActiveSkyhttp://www.hifisim.comhttp://www.hifisim.com/images/as2004betateam.jpg

Oh please Vic, dont "refrain" from what you really think. LOLAny way, I re-read the comment I made and "disaster" was definitely disrespectful. My apologies if I insulted Damian. That was never my intention. I too was waiting in anticipation for the release of this product and I rest assure in time it will be a winner. I'm just a little surprised that the issues were not discovered by the "beta team" which could have assisted Damian in his efforts.Its obvious there is definitely some issues currently with the product evident by many complaints posted here and about the web. And yes I do understand that some products hit the market with minor issues that need addressing. MSFS is a good example of this. My intention was only to see if I could generate some confidence from "those who know" (sorry vic), that they anticipate they will be addressed soon. Again, I am more than aware that the delayed release of the SDK handicaps any developer.Damian, if my comment was insultous, please except my apologies. I look forward to purchasing this product very soon. Happy Holidays.Mike(Just a note - I just bought the product and anticipate getting it setup.)

Beta Testers didn't experience your problem Norm, because it didn't occur throughout the beta testing period. Had it occurred, it would have been investigated, and fixed.I used three different computer systems (all spec different),three different keyboards and three different mouse during the beta test phase in order to identify and help eliminate bugs etc. Not once did I have a keyboard lockup or any problems with the mouse. Not once did I come across your problem Norm.As with a lot of the beta testers, we all run different computer systems and a variety of flightsim add-ons (both payware and freeware) and had identified various conflicts between programs/add-ons. Unforntunately, we can't all have the same add-ons etc that everyone else has on thier system, and can't identify EVERY issue that some user may experience, whether it be due to his/her system type/configuration, add-ons or both.A lot of problems users experience are directly related to initial configuration issues and not reading and digesting the users manual.ActiveSky 2004 was definately ready for release!!Maybe you can send us your 'cranky computer and key board' for the next round of beta testing.David