Jon Patch

Wednesday, February 28th, 2007

Vancouver+1 Part 1 (City and Landscape) for FSX update

Filed under: Development, FSX, Flight Simulation, Flightsim, Vancouver — jonpatch @ 4:19 pm

Holger and I are working away on this right now.  Holger’s recent Bella Coola release (download here) allowed him to learn a lot of the nuances of FSX.  And Ron Zambrano is doing a bunch of AI floatplanes for FSX for us.  We’re not ready to announce a release date, for one thing we would like to test on the upcoming FSX SP1 patched version, and no release date has been announced for that.

We are discovering that it’ll be best to continue use a number of FS9 techniques in this release: either the tools aren’t available yet, or there is not a known way to implement what we want in FSX.  Examples are seaplane AFCADs (FSX won’t accept the invisible runway technique) and LWM3 polys (land-water masks that have slope).  As well, unless anyone comes up with a solution, we won’t have heli AI at elevated pads, which was a very small part of the release anyway.

I’m back on the Lion’s Gate Bridge now and will post shots as bits come together.

Some cool stuff from Sebby …

Filed under: Healing, Learning — jonpatch @ 4:09 pm

Sebby (Sebastien St. Laurent) has taken a break from the ACES for a couple of months to re-group.  His honest post about his personal journey is refreshingly frank.  Thanks, Sebby!

Friday, February 23rd, 2007

A tickler on FSX performance in SP1 from Paul Lange

Filed under: FSX, Flight Simulation, Flightsim — jonpatch @ 7:48 am

Paul Lange suggests in this post, that the performance increase target for FSX SP1 is 20%, +/- a bit depending on configuration … and of course that brings up a question or two: Will dual cores be better utilized?  Will systems with video cards with 512Mb of RAM see a better increase?  Will the high autogen hit be improved?

Wednesday, February 21st, 2007

For developers: more detail on what will won’t be addressed in FSX for SP1

Filed under: Development, FSX, Flight Simulation, Flightsim — jonpatch @ 2:16 pm

Phil Taylor has a couple of notes on issues of importance to developers.  Particularly critical for developers of large detailed airports is the report that the “round-earth” issue will be partially addressed: “short” polygons should be ok, while “long” polygons will still suffer from issues related to divergence from the earth’s curvature.  However this looks like it’s focused on runways, not necessarily on the FS2002 ground polygons so important for ground detail.  We’ll see how they work.

Wednesday, February 14th, 2007

News on FSX Service Pack 1

Filed under: FSX, Flightsim — jonpatch @ 2:40 pm

Phil Taylor reports that work on FSX SP1 is 85-90% completed, then it’s off to extensive testing.  So it’ll be a while before we’ll see this.  Phil states that some broken third party addons from FS9 will benefit from some fixes, and provides some screenshots (although as of this writing some of the links are broken).  I’m pleased to see from the screenshots that a dusk rendering bug that left the ground textures at dusk dark and bland has been fixed.  However it doesn’t look like the bug that causes building textures during dusk to be dingy has been addressed. 

Dusk was very impressive in FS9 and looks like a power failure in FSX as it stands, so this is good news.

Saturday, February 10th, 2007

And another list of Business Plan sections

Filed under: Business — jonpatch @ 10:08 am

I listed in my last post the sections of my business plan, but I also have a more general checklist of sections I use with clients, large and small.

Tips

·        Be clear who your audience for the plan is: is it just yourself?  Will it also be for employees? Investors?

·        Concentrate on getting a first pass at the plan completed, it’s easy to spend too much time collecting data instead of getting it done.  You can refine later.

·        Be prepared to find creating a plan is much more difficult than writing some ideas down, it brings flaws and conflicts to the surface.  Spend the time to uncover the source of the conflicts, and resolve or reconcile them.

·        Have 2 or 3 people you trust review the plan.  If possible these reviewers should have expertise in the business area(s).

·        Keep the plan as simple and short as possible while answering all key questions. 

·        The greatest value of the plan is in the process of its creation, not the final product.

·        Make sure it works: following your dreams may mean operating a couple of business areas to ensure that the bills are paid, when you might prefer to stick to one that doesn’t provide enough income.  Some people start businesses while still employed to maintain cash-flow. 

Plan Sections

1.       Executive Summary.  (The Two-Pager) If the plan is intended for soliciting investment, a two-page Executive Summary can outline the Market opportunity, the business model, and the rewards.

2.       Introduction.  Explain who wrote the plan and why.  Who is the target audience?

3.       Objectives.  List your objectives.  For the sole or joint entrepreneur, this may include more than financial goals: sense of accomplishment, satisfaction from reaching goals, interaction with people.  Summarize the product and market in one or two sentences.  Describe your vision (what will the business be like in 3 years) and the action you will take to realize that vision.  (Together those two components are the mission.).  What are the values you want to instill in the venture?

4.       Opportunity.   Identify the opportunity or opportunities you’ve identified that will help you reach your objectives.  Answer some key questions: how is this unique? What is the competitive advantage?

5.       Business Area(s).  Describe in a paragraph each the service or product area(s) you envision.  Keep it short and clear.  Summarize the business model for each: how do you make profit?

6.       Assets.  For the entrepreneur, assets can include education, training, experience, attributes, and personal network.  There may be intellectual property (IP) or other technological know-how that is important, or physical assets: equipment, office furniture, etc.For larger ventures, this section may be replaced by an Intellectual Property/Proprietary Information section and personnel descriptions in the Key Personnel section.

7.       Strategy.  Summarize briefly your high-level vision of how you will realize your objectives: will it just be yourself and your team?  Are there important strategic partners?  Where will the majority of your time be spent?  Will the venture be self-funding, or need investment?  For a larger business, the Strategic Plan may be a separate document.

8.       Market.  Outline in more detail your target market: demographic, geographic, industry, and the market maturity.  Specify what you think the market size is and will be.  How has the market changed?  How do you anticipate it changing?

9.       Operational plan.  Describe your existing and planned infrastructure requirements.  Include office, communications, web, and any other physical facilities.Include a schedule for operational improvements, including capital expenditures.Describe your staffing/outsourcing plan, including subcontractors.

10.     Research Plan.  If technological research is a key factor in the venture, describe the research areas, how the research will be conducted and the desired outcomes.

11.    Marketing & Sales Plan.  How will you reach your market?  Word of mouth? Viral marketing?  The Web?  Advertising?  Direct sales through cold calls?  Existing business relationships?  What market research do you plan to do?

12.    Key Personnel and Service Providers.  Describe the qualifications of founders and key personnel.  Identify key external suppliers: raw materials, legal, accounting, etc.

13.    Risk Management.  List risks and the mitigation plan for each should the risk occur.  Include sales, financial, environmental, liability and intellectual property risks.

14.    Financial Plan.  Project your cash flow out over two-three years.  If you have financial planning expertise or resources, you may want to have a separate Profit and Loss (P&L) statement and Balance Sheet (Assets and Liabilities).  For small businesses with a short latency or no difference between the financial transaction and showing these entries on the books, the cash flow can serve as your P&L.Often it’s useful to do two projections, or even three (“Sensitivity Analysis”): Optimistic, Pessimistic and Most Likely.  State the assumptions that each projection is based on. Some folks even create a fourth from these, combining these three with different weightings.  A suggested weighting:

Expected = 0.3*Pessimistic + 0.6*Most Likely + 0.1*Optimistic

You may discover you need financing: in this case the Business Plan is how you will communicate the opportunity to investors.  Show clearly the return on investment and realistic timeline.

15.    Appendices.  Here you can provide details for later reference.  Appendices can include education, training, industry and product experience, international experience, client/employer list, work experience summary (=accomplishments), community service, more detailed financial information, support resources or anything else that isn’t critical to the body of the plan, but you want as handy reference.

Thursday, February 8th, 2007

Meanwhile, in the real-world

Filed under: Business, Development, Flight Simulation, Flightsim — jonpatch @ 10:48 am

With the substantial completion of my little corners of Glacier Bay, I’m taking a break this week from FS for some business planning for the next couple of years.  I want to balance the FS development with my contract services, and that requires that I put follow my own advice and bring my business plan up to date.  So over last week and this, I’ve completed a draft, sent it to my trusted advisors for review, and integrated their sage comments into my plan.  Here’s the sections:

  • Opportunity
  • Objectives
  • Business Areas
  • Assets (education, training, experience, attributes, network)
  • Strategy
  • Marketing (Market definition, plan)
  • Infrastructure
  • Implementation Plan (which includes milestones, allocation of time to each business area, etc.)
  • Risk Management (list of risks and mitigation for each)
  • Financial Plan
  • Appendices (details on education, training, industry and product experience, international experience, client/employer list, work experience summary (=accomplishments), community service)

Much of this material is fodder for specific client proposals: I can pick out the relevant info easily from the boilerplate. Although all the plans I create or facilitiate have essentially the same sections, no two are ever the same.  I think it important to tailor the plan to the opportunity.

Monday, February 5th, 2007

Skagway ready for Beta2

Filed under: Development, Flight Simulation, Flightsim, Skagway — jonpatch @ 10:07 pm

With the completion of the night textures and the tying up of a few dozen loose ends, I’ve released Skagway to Holger for beta 2.  There are still a few minor bugs.  Here’s some screenshots. 

Holger and I independently caught one FS9 bug we’d never noticed before: the MS generic storage tank model we used has a transparent alpha channel, and the assigned area of the night texture is black.  Net result: they disappear at night!  This would have been true for some of the tanks on the side of Burnaby Mountain in Vancouver+ Part 1 as well.  Anyhow, the proposed fix will patch FS9 for everyone.  (BTW MS fixed this in FSX)

EDIT: Here’s a hi-res bonus shot of looking off to the right on final approach on 02.

The Veendam at dusk.

Overview of the port facilities.  For a hi-res version click here.

Veendam and Dawn Princess.

Container Yard (click here for hi-res version)

Saturday, February 3rd, 2007

Camel Point aircraft

Filed under: Aviation - Real world, Victoria — jonpatch @ 6:22 pm

The Helijet folks at Camel Point Public Heliport (CBF7) in Victoria were kind enough to let me airside to take a few pics.  First is the S-76, then the venerable S-61 in its distinctive black and white livery. These images are larger than what I usually post, so I’ve provided links.

S-61 C-GBSF Low-res

S-61 C-GBSF Hi-res

S-76 C-GHJW Low-res

S-76 C-GHJW Hi-res

Thursday, February 1st, 2007

Now this is a bit more realistic …

Filed under: Development, Flight Simulation, Flightsim, Skagway — jonpatch @ 6:13 pm

Sunny days in Skagway are not common in the summer … so these shots may be a bit more realistic.  To ease into reality, we start with one sunny shot.

Next we see the Veendam … this shot is the only one not at native resolution: it’s been resampled from a larger screenshot and slightly sharpened.

Then Larry’s lovely marina behind the Veendam, which Holger has now populated with boats.

Yippee!  The berths on the East shore have appeared!

An overview of the container yard.

And lastly, a little wobbly on the 20 approach coming out of the valley …

Older Posts »

Blog at WordPress.com.