Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Love it.

Featured Replies

Well, shucks, Scott...I wonder how you'll do when we roll out the combination: A G1000-equipped B200 with Blackhawk Mods.

 

:-)

 

The C90 is already on the big side for me, and the Mustang on the edge due to the G1000. The C90 won me over pretty easily, but the Mustang with that durned full glass cockpit is taking a bit longer. Still working on it, though. Maybe by the time you roll out the B200 I can tackle both my size and glass cockpit phobias! I'm a complex piston/analog gauges kinda guy, so I must put up at least token resistance! It's a personal thing...

 

Scott

Love em both; the Malibu and the C90:) Shows what hard work and good textures can really do in this old dog of a program!

Simon

Extracting info (any info) out of that bunch over on the Flight1 forums is like pulling teeth from a Goldfish...

 

Besides this obsessive-secretive nature that most FS developers have towards releasing any info about projects is a bit childish... and serves no real purpose. Beyond maybe that of feeding their own ego's...

 

Especially once the project has progressed beyond a point where its clear the intent is to make it and release it...

 

I can understand not telling everyone about all the projects you like to make, or ones you doing research on... but once its clear you ARE going to make it, and its in production, then why not tell folks.

 

The secretive-hush-hush attitudes so pervasive throughout the FS Dev Community speaks to a broader character at work...

 

Keeping projects from your customers is a bit naive...

 

Part of the excitement we as customers have is watching a project evolve and develop... seeing screenshots of the WIP and small informational posts now and then as the project gets closer to release.

 

We never get that with Flight1... infact we hardly get that from any developers...

 

The outwardly appearance of some developers is they are not producing anything... nothing out of them for months, even years... then ***POOF*** a plane, or scenery package... then nothing again for months or years...

 

Don't take this post personally, I'm just venting in general.

 

I think we, the forum users have caused this ourselves.

 

Any new development attracts a bunch of impatient folks that start

beating up on the developer for not releasing the project sooner, and then, as soon as it

is out, start beating up on the developer for not having tested the project well enough,

because they find something wrong with it.

 

As a developer you need a thick skin, and frankly best keep your mouth shut until you are

ready to ship, if you want any peace in your life..

Bert

Well, shucks, Scott...I wonder how you'll do when we roll out the combination: A G1000-equipped B200 with Blackhawk Mods.

 

I AM DROOLING.....

 

I have been flying the F1 Stang since its release....... The whole F1 G1000 platform has become more stable for me as it matured.....but add Blackhawk mods!!!!!!!!!!!!! Does F1 want some $$ now? lol

 

BLR Winglets??? lock it up....

  • Author

Extracting info (any info) out of that bunch over on the Flight1 forums is like pulling teeth from a Goldfish...

 

Besides this obsessive-secretive nature that most FS developers have towards releasing any info about projects is a bit childish... and serves no real purpose. Beyond maybe that of feeding their own ego's...

 

Especially once the project has progressed beyond a point where its clear the intent is to make it and release it...

 

I can understand not telling everyone about all the projects you like to make, or ones you doing research on... but once its clear you ARE going to make it, and its in production, then why not tell folks.

 

The secretive-hush-hush attitudes so pervasive throughout the FS Dev Community speaks to a broader character at work...

 

Keeping projects from your customers is a bit naive...

 

Part of the excitement we as customers have is watching a project evolve and develop... seeing screenshots of the WIP and small informational posts now and then as the project gets closer to release.

 

We never get that with Flight1... infact we hardly get that from any developers...

 

The outwardly appearance of some developers is they are not producing anything... nothing out of them for months, even years... then ***POOF*** a plane, or scenery package... then nothing again for months or years...

 

Don't take this post personally, I'm just venting in general.

 

Spoken like someone who's never been raked over the coals for missing a projected release date - or had to deal with a sea of "when are you releasing it" forum posts. Most developers keep their projects quiet during development for a simple reason: they'd rather spend their time developing than being second-guessed by an army of forum bystanders.

 

I hope that doesn't sound too bitter, but having been there myself I understand completely why any developer would rather wait until a product is in beta before talking about it.

I agree with Bert and Bill. I can think of several projects where putting out an expected release date caused some forum ripples...the C90 is one of them.

 

I also think it's unfair to apply a blanket "goldfish teeth" analogy to the information provided by Flight1...for months prior to the release of the Mustang, there was a website dedicated to general information about the Mustang, and the open area of the Mustang forum was up and running well in advance of release. There is significant risk in that, from a developer's point of view -- projects like flight sim addons are generally put together by small development teams (The Mustang was five guys, if memory serves, and the Aeroworx B200 was just three), mostly folks working part time. Every member of the team is critical, and if someone drops out, the whole project suffers, often to the point of being scrapped altogether.

 

There are many times when the details of a project are fluid through much of its development timeline. Features are discussed, even planned, and then turn out to be impractical for whatever reason. Announcing them in advance without following through would generate tremendous forum backlash that could negatively affect sales to the point where a project is in danger of failing to recoup its own expenses. Just as often, features everyone hopes for are thought to be impossible until shortly before release, when one of the developers has an "aha! moment and puts it all together. Saying "we're not going to do that" is a guarantee of negative forum talk ("Well, if the framjammit isn't simulated, I'm not buying it!") and that also has a negative impact on sales that can't be fully saved by releasing the thing with a bold banner announcing that the framjammit is included after all. It really is better to just keep quiet until you have something worth showing everyone, and from a very real business perspective, it's hardly naive.

 

Anyway...I've bogarted this thread long enough. I think I'm gonna go fly a few short field approaches in the C90B.

Best Regards,

Kurt "Yoda" Kalbfleisch

Pinner, Middx, UK

Beta tester for PMDG J41, NGX, and GFO, Flight1 Super King Air B200, Flight1 Cessna Citation Mustang, Flight1 Cessna 182, Flight1 Cessna 177B, Aeroworx B200

Well, shucks, Scott...I wonder how you'll do when we roll out the combination: A G1000-equipped B200 with Blackhawk Mods.

 

Really looking forward to this one, and understand completely the reasons for not giving any release dates. I'm sure it will be worth the wait :Loser:

 

Martin

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.