Marniftarr

The worldcam camera list excluded from cycle now. If you press "Next category" button , you will switch cameras between VC and Aircraft lists only. If you call any worldcam camera , you can use cycle switching ("next camera") between worldcam cameras inside worldcam list.

I explained the reason on which it is impossible to set effects on the cameras FSX. An external application can't know what the camera you selected. For this reason an external application such as EZCA or any other can't apply the necessary algorithm of jolting to this camera. I can make one effect for all cameras. But jolting on a wing will be same as jolting in the virtual cabin. Sorry but I do not understand value of such addon.

I not completely understood about what you speak. But I will try to explain the reason of association of two absolutely different functional products - a shake-up + camera manager. Long ago in 2008 I decided to write the small utility which allows to walk on FSX space. Started to study SDK. After some time I wrote WalkCamera which used some possibilities written to SDK. Once I seen total absence of dynamics of the near plan in FSX. In the real fly you not see a shake, but you feel a shake-up by bum. The only way to transfer these feelings to a simmer is a shake the picture before his eyes. So the decision to write to EZCA was made. But only having begun the project I met insuperable difficulties: SDK doesn't provide any information on a name of the current camera, type, class and event of camera change name. Anything, except information except that when you are in a virtual cockpit or out of a cockpit. No more.... How to make jolting effects for FSX cameras without this information I don't know. Shortly - SDK doesn't provide any information concerning names of FSX cameras. Making effects for FSX cameras is impossible. Project under the threat. If SDK gave such information - I simply would write effects of cameras and NO any manager. The unique way out - the external manager of cameras and stick shake effects to EZCA cameras. With manager i know camera name , know type of camera and I can make database of effects. As a result there was a manager as a compulsory measure for the correct work of effects. I not completely understood about what you speak. But I will try to explain the reason of association of two absolutely different functional products - a shake-up + camera manager. Long ago in 2008 I decided to write the small utility which allows to walk on FSX space. Started to study SDK. After some time I wrote WalkCamera which used some possibilities written to SDK. Once I seen total absence of dynamics of the near plan in FSX. In the real fly you not see a shake, but you feel a shake-up by bum. The only way to transfer these feelings to a simmer is a shake the picture before his eyes. So the decision to write to EZCA was made. But only having begun the project I met insuperable difficulties: SDK doesn't provide any information on a name of the current camera, type, class and event of camera change name. Anything, except information except that when you are in a virtual cockpit or out of a cockpit. No more.... How to make jolting effects for FSX cameras without this information I don't know. Shortly - SDK doesn't provide any information concerning names of FSX cameras. Making effects for FSX cameras is impossible. Project under the threat. If SDK gave such information - I simply would write effects of cameras and NO any manager. The unique way out - the external manager of cameras and stick shake effects to EZCA cameras. With manager i know camera name , know type of camera and I can make database of effects. As a result there was a manager as a compulsory measure for the correct work of effects.I not completely understood about what you speak. But I will try to explain the reason of association of two absolutely different functional products - a shake-up + camera manager. Long ago in 2008 I decided to write the small utility which allows to walk on FSX space. Started to study SDK. After some time I wrote WalkCamera which used some possibilities written to SDK. Once I seen total absence of dynamics of the near plan in FSX. In the real fly you not see a shake, but you feel a shake-up by bum. The only way to transfer these feelings to a simmer is a shake the picture before his eyes. So the decision to write to EZCA was made. But only having begun the project I met insuperable difficulties: SDK doesn't provide any information on a name of the current camera, type, class and event of camera change name. Anything, except information except that when you are in a virtual cockpit or out of a cockpit. No more.... How to make jolting effects for FSX cameras without this information I don't know. Shortly - SDK doesn't provide any information concerning names of FSX cameras. Making effects for FSX cameras is impossible. Project under the threat. If SDK gave such information - I simply would write effects of cameras and NO any manager. The unique way out - the external manager of cameras and stick shake effects to EZCA cameras. With manager i know camera name , know type of camera and I can make database of effects. As a result there was a manager as a compulsory measure for the correct work of effects. Anyway possibilities to transfer feeling of flight from the screen of the monitor aren't finished. in v2 jolting will be correct on all physics laws. Microsoft made a wonderful world of FSX, but dressed on the head of a simmer a bucket, poured over it concrete and sticked to a seat - the flight without feelings of flight... The feeling of driving on rails is created by Micr.. FSX is not a train simulator. Another short video: http://www.youtube.com/watch?v=J6vtO5KHu5A

Look this: http://www.youtube.com/watch?v=K2GVtGdsXrM&feature=related In real world the wing of some gliders is bent much more than in FSX. I strengthened effect for the show.

Impossible, because this is a explained SDK function. FSX have not this function..

Please do not ask me about release date :-) i do not know. May be in middle of october. The engine V2 is remaking every time , when i find new idea. For this necessary some time.

So, V2 is not dead! === We took pause because we did not know how to improve EZ effects. There was a big pause in development. We didn't know how to advance idea in order that effects were realistic. To many hours of flight time in real are necessary for solving this problem. The whole summer was in real flight. Now we know what should feel the simmer and how do this. I see on the wishlist that the user interface will be simplified. === The user interface didn't become simpler. The simulator doesn't provide necessary data for simplification of the user interface. Many data are necessary for synthesizing means of an engine by EZ. All synthesis of data laid down on shoulders of the user of EZ. But we plan to expand a database for cameras. Most likely you will find a necessary set of cameras for your airplane in the list of data base . Now we think that the user couldn't model effects and used the cameras adjusted by a skilled eye because modeling of camera shake is really difficult and demands a certain skill. The user can change only shake levels, but not algorithms.

Hi, everybody. The EZCA v2 project approaches to completing blueprint stage after a big pause. Before release I want to show new effect (the camera is attached to a flexible wing). It will be possible to feel all dynamics of behavior of the airplane during flight. (only on those models airplanes on which wing bending is provided). The effect will be switched on in the new version as a part of a new physical engine. Look this: I ask to evaluate working of this effect and speak any impressions. I will listen to any criticism. The effect is strengthened for demonstration. Not all. Besides other, in the new version the algorithm of shaking is completely remade. Now it is not irritating static effect of a shake of the camera, now effect depending by a state of environment and depending by a manner of piloting of the plane. For example at excess of critical angles of attack at great speed the plane will shake and it can be seen.

.

Hi guys. I updated video:http://www.youtube.com/watch?v=QurMXcu2aaEThe thrust+engine test. Is it naturally ?

What it is "helo" ? Explain me.

Second, is "flatter" meant to be flutter or is it another phenomenon I am not familiar with? I would be very interested in seeing the types of vibrations created from lower the flaps and gear and I am wondering if this is related.===Flatter .. Flutter .. How is correct ? - This effect will arise if you make overspeed. The wing will have very big small vibrations. If you will increase overspeed - the aircraft will collapse.I know this effect as "flatter" or "Flutter" .. How correctly in English ?I wonder how the new turbulence effects will interact with wingflex.===wigflex like here ? http://www.youtube.com/watch?v=psluSHkQ3GQI can't simulate a wing bend if you looking to wing from the passenger or pilot seat. I can simulate a bend of a wing at the sight of from the wing end on the pilot or the passenger. The storm will bend a wing.Video a bit later.

I'll add a +1 on making the manual implementation / interface more user friendly for the layman. That's what scared me away from ever purchasing it reading all the comments in the past. How about a video of the interface and how one sets up the program when that part is ready?===For non professional users i make simple interface where you can do simple operations like on/off effects , reduce shake level and change global tone of shakes . No more.For professional users i make effect studio , but in first versions i will not give PDF manual , but i give video lesson where professional can see operations and methods for adjustments and create effects. Probably the video will be on Russian.The new EZ engine very hard for study and explanations for non professional users. But if you understanding effect studio 1.17 and if you understand base "how do effects ?" you can understand new EZ engine with my video lesson even with Russian language.

Hi all !I am surprised that video for developers immediately was displayed at this forum. It means that adding still popularly among simmers.About date of release V2. Me often ask when? I can make release now , but I am not able to do it now because I want to implement the ideas as much as possible qualitatively. Each new singularity demands the durable time of testing. Creation process v2 becomes complicated repeatedly because new singularities are interconnected with each other and if I am dissatisfied with one singularity, I am forced to alter more half of code. Since March of this year I rewrote the code four times. Besides, I have family duties.But I work and I want to make v2 as much as possible approached to real.Me often ask a difference between 1.17 and V2?New singularities v2:In air and on the earth the airplane body vibrates now. It is visible on it video:http:// www.youtube.com/watch? v=aVV-5LUc-ikIt means that there is no more illusion of jolting. There are real oscillations of a fuselage and real oscillations of the camera from fuselage oscillations.The small weather engine is added. EZCA defines turbulence level in a cloud layer in which you fly and EZ sets level of fuselage oscillations. It means - no more RND oscillations now. There are oscillations which depend from turbulence level.Additional jolting from level release flap and gears is added. If you let out the chassis or flaps at great speed - the plane will shake as in the real world. Level of additional jolting depends on speed of the airplane.Shakes from overspeed and flatter will be added later.Shakes from engine RPM is added. Shakes by a propeller force is added when the airplane stay on the brake. It is visible on my video.The manager of cameras:The banking axis is added. Now the camera can be incline. ZOOM now works through DMA. Now it is possible to set any value ZOOM. Simconnect doesn't allow to set below 0.3. On wide and big monitors with the big resolution it is necessary to install ZOMM more low 0.25. Now it is possible.Now the configurator doesn't modify aircraft.cfg files of each plane. Now there is no necessity reconfigure FSX after adding of the new plane.If the database of effects and cameras doesn't exist for the new plane - EZ will add cameras and effects automatically. The user just should place positions of new cameras using Nun2.Also . The v2 will be free for previous EZ users.Please be patience and use old version before release v2.