Leaderboard

l'aéro Cusp Whee And around we go Just Buzzing Bringing sexy back

Working from some excellent references provided by jeanba, I'm developing skins for French N27s stationed in Italy in 1917/18.

You just need better ATC for it :)

Royal New Zealand Air Force Canberra B(I).12 Interdictor through the years 1959- 1970. Used in action in Operation "Confrontation" against Indonesia 1964- 1966

Let's start with something that's kind of a corner case but irritates me greatly on my Madagascar/Mozambique install. Stock Frequency : The frequency at which the bug can be reproduced in a full stock game, from 0 (Never) to 5 (always when following the conditions). Specific Frequency : The frequency at which the bug can be reproduced in the specific game setup, from 0 (Never) to 5 (always when following the conditions). Severity : How bad the bug is. 1 (occasional annoyance), 2 (Recurring annoyance), 3 (Immersion breaking, game can be played, missions won, but things are weird enough you're constantly aware of it), 4 (Gameplay breaking) or 5 (Game breaking/crashing/freezing/CTD). Test environment : Either stock, a link to the necessary files, on demand so people interested in testing and reproducing can contact the bug reporter to obtain the necessary files, or closed if for some reason the bug reporter can't provide a test environment. Environment : July 2013 patch-level, SF2NA. Only in Single Missions, on NavalMap. In non-stock installs. Conditions : If the only bases available to player are carrier groups and off-map bases. If there are multiple friendly nations with player available planes. If the player tries flying an ESCORT mission for a service other than FriendlyNation001. If FriendlyNation001 only has planes using a MinBaseSize larger than the carrier generated for the player. Expected result : The engine generates a flight of the same nation to be escorted by the player, based on the same carrier group. Result : The engine generates a flight to be escorted only from FriendlyNation001, but failing to assign a plane with the right MinBaseSize (because it doesn't exist), assigns one from the next available size (effectively trying to have MinBaseSize=MEDIUM planes take off from a CarrierBaseSize=SMALL carrier) leading to the flight failing to populate and a mission that can only be failed by the player (since the ESCORTed flight never takes off, it can never reach its objective, automatically making it impossible for the player to achieve his own). Other missions non-player flights are similarly afflicted but since they are non-essential to the player's own mission, their failure to populate has no impact on the player apart from skies mostly empty of friendlies. Land bases in similarly constrained situations do not seem to suffer from the same problem as the engine seems not to limit itself to the planes available to FriendlyNation001, more controlled testing needed to validate it. Stock Frequency : 0 Specific Frequency : 5 Severity : 4 Test environment : On demand Potential fixes : - Instead of defaulting to FriendlyNation001 for the escorted flight, default to the player's nation. - Provided there is another friendly carrier station on the map, populate another carrier group from FriendlyNation001 to serve as a base for the escorted flight.

Deja vu?

Progress shots below of an experiment, showing Nungesser's Nieuport 24. We are trying to figure out a way to run multiple versions of one aircraft ingame, each utilizing dedicated artwork, or decals, or both.

Dear Friends, Today I would like to tell you about what we plan for Flying Circus – Volume One and show you some WIP screens of our first two aircraft which are ready for Early Access release this month! But first let’s take a minute and talk about how we came to make Flying Circus and the challenges that we face in developing it. Of course, Flying Circus is going to essentially be our spiritual sequel to our ground-breaking WWI simulator Rise of Flight: The First Great Air War. ROF was the first product we ever made and over the course of several years we greatly expanded its content and created some really cool features for it, many of which were ported or updated to work in Sturmovik. We have not lost our affection for WWI and we have always hoped to be able to bring WWI combat to our updated Digital Warfare Engine. When we eventually ended work on ROF and shifted our focus to WW2 many WWI fans were disappointed. At the time, we had no intention of abandoning ROF or her fans, but the requirements for WW2 overwhelmed us and we had no resources to manage two projects at the same time and the technology we developed for WW2 was extremely difficult to retrofit back into our WWI engine without causing major delays to Sturmovik. Retrofitting WWI would have required an entirely new team of developers that we could not afford. So, we marched forward with WW2 hoping to someday find a way to come back to WWI and do a sort of parallel development. That opportunity has finally become available thanks to some creative planning and so we decided to create Flying Circus – Volume One with the help of our friends at Yugra Media. Yugra employees have been training with our team learning how to re-build our WWI content and make maps with our current technology. This has taken several months already, but our plan is to get WWI up and running as quick as we can and get WWI content brought up to our new standard. We hope to generate new revenue to fund more WWI development and general development of the common engine which benefits all of our products. We also wanted to give WWI fans something to cheer about after a long drought of development. Now it should be said that trying to bring all content and features of ROF to Flying Circus in one fell swoop is impossible. This will be a marathon, not a sprint and new features or old features found in ROF will take time to make in the current engine. Bringing WWI to our current engine which has been re-worked and modified for WW2 is a big challenge and some things can be ported relatively easily and others require all new work. As with Tank Crew, several months of work behind the scenes has already taken place laying down the foundation to support Flying Circus. This will take much time, but we will endeavor to make Flying Circus just as awesome or even more amazing than ROF ever was. However, for that to happen we need your support! Both Flying Circus as well as Tank Crew are experiments and first steps in working with qualified and trained third parties on new content and gameplay features that users have asked for or we feel have potential to help our overall cause. Our team is still small, relative to our competitors and we are still a self-sustaining team. Meaning, we sink or swim on our own, there are no bailouts if we fail regardless of who our benefactors have been in the near past. So, if you like anything about Flying Circus please support us by buying a copy. We want to make WWI great again inside the Sturmovik universe. So now that you know the background of how Flying Circus came to be, let’s take a look at the actual product. As you have previously read in other announcements here are the planes that will be included in Flying Circus – Volume One. We have decided to choose a plane-set that represents the period of April-May 1918. This period offers some great planes that will provide lots of fun match-ups. Planes: Spad XIII Sopwith Dolphin Sopwith Camel RAF S.E.5.a Bristol Fighter Albatros D.Va Fokker Dr.1 Fokker D.VII Pfalz D.IIIa Halberstadt CL.II. The first two planes off the assembly line and into Early Access will be the venerable SPAD 13C.1 and the Fokker Dr.1 triplane! All of the planes in Flying Circus have their roots in ROF, but the models have been re-worked by Yugra Media to be brought up to our current visual standard. That means improved mesh and new 4K textures. Map and Technologies Included will be a map that is approximately 100 km x 100 km that has is generally centered on the Arras sector of the Western Front. The map will include towns such as Arras, Cambrai, Lille, Amiens and St. Quentin and the dreaded No-Mans-Land along with several airfields to fly from. This map will be created using all our latest map making technology that is found in current IL-2 Great Battles products. It should make WWI a much more beautiful experience scenery wise. Matter of fact, Flying Circus will benefit from all current and new technologies in our updated engine. This means more than the graphical updates, but also improvements to AI and of course our amazing VR support is included! The difference from ROF will be quite remarkable. The plan is for future volumes of FC to include larger maps like we had in ROF. Exactly how big, is yet to be determined. For us to bring WWI to you in any reasonable amount of time, we have decided to use the Flight Models from ROF for our Flying Circus planes. We have done this for a couple reasons. First, we have spent a lot of time researching and building these FMs over a period of several years and unlike the 3D models, they stand the test of time and there is no reason to toss them and start over. Second, these FMs were built for an engine that was created solely for WW1 speeds and maneuvers etc. It was more prudent to build support for these FMs in the current WW2 focused engine, then to completely re-make these FMs with an engine designed for heavier and faster aircraft in WW2. In essence, we’ve been able to make both regimes co-exist side by side within the same environment without compromising the feeling of flight or their unique characteristics. Our engineering team as done a marvelous job building this support in just a few months! Without this work, Flying Circus would not be possible. Our Flying Circus planes will still have all the interesting quirks and characteristics that many of you know and love from our previous title. Finally, I must mention one of the driving motivations for making Flying Circus at all - VR support! There was simply no way to retrofit VR support into ROF properly. So, to bring our awesome VR support to the WWI battlefield we had to work on a new title with the tech already included. The end result did not disappoint, we really like how our open cockpits look in VR! This will be a really awesome experience for those that love VR. Features As I mentioned above, getting WW1 up and running again takes a lot of work, so Flying Circus will initially include support for the Quick Mission Builder and our Mission Editor. We will also create and include some custom single-player missions as we near completion of FC and if Volume One proves popular and we move to make future volumes, we will introduce the Pilot Career to FC. And Scripted Campaigns can be built for FC by anyone using our Mission Editor just like in IL-2. If you are concerned about the Pilot Career, please know this. We can’t support the Pilot Career for FC yet because we are still building support for WW2 and other general features and mission types it needs. Remember, it’s still new tech for the Great Battles series and we have to build this support in-house so we cannot place this task with a third party. We also have to build support for WW1 style missions and this will take time. If we include support for the Pilot Career in say Volume Two of Flying Circus, it will of course become compatible with Volume One. That is the beauty of our one client approach. All of our Flying Circus aircraft will come equipped with all field and factory mods that we used to sell as separate items way back when. This also includes pistols, scarves, streamers and special gunsights like the Aldis and collimator style gunsights. And last but not least, our pilot models for Flying Circus will be completely new and they will look really cool in our updated aircraft. They of course have yet to be animated, but the finished pilot models look to be really great! We hope this overview of Flying Circus is helpful and gives you a good idea of the great effort we are undertaking to bring WWI development back to our amazing WWI fans who enjoyed Rise of Flight so much. So please enjoy the following images of Flying Circus. Remember this is still a Work-in-Progress and the maps is obviously not WW1 France. For Early Access we will be including the Lapino map as a substitute until the French map is ready. You can discuss the news in this thread