Marniftarr

Commercial Member
  • Content Count

    139
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Marniftarr

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    IVAO
  • Virtual Airlines
    Yes
  1. Marniftarr

    EZCA v2 news.

    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.
  2. Marniftarr

    EZCA v2 news.

    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.
  3. Marniftarr

    EZCA v2 news.

    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
  4. Marniftarr

    EZCA v2 news.

    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.
  5. Marniftarr

    EZCA v2 news.

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

    EZCA v2 news.

    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.
  7. Marniftarr

    EZCA v2 news.

    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.
  8. Marniftarr

    EZCA v2 news.

    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.
  9. Hhmm. Good idea. But one question ! How precision in nunchuk ? Track-Ir have absolute coordinates and have resolution 720x575 points. Touch pad have absolute coordinates and resolution 4600x3200 points. How resolution if i move nunchuk in 3-5mm right or another side ? I want use nunchuk as low price alternatve Trac-Ir device. Can i move head in VC with use nunchuk with your software ? (not for controls aircraft)..
  10. This "nunchuk" place on head and have alternative track-ir device ? hmm.. I have Track-Ir 4pro today. But my neck is dead after use track-ir. In touchpad i see alternative device for my fingers but not for neck.===Christian ! ! ! One question ! Where i can read info about your "nunchuk" device (or connection method) ? It is idea interest too ! Can i read "nunchuk" SDK for make advanced software for FSX ?
  11. HI ! All ! This is a second video about this device . I`m in shock ! You can move body in VC as Trackir ! HOW ??? Author this video under shadow :-(( http://speedskater.ru/download/arccvid/touchviewp2.wmvAuthor !! Where are you ? I have more questiions about it !
  12. Hi All ! Look this wideo ! This is a new alternative panoramic device aka hat-switch but in analog mode (touchpad from notebook in Saitek X-52) ! How idea ? Video 18mb 3 min.http://speedskater.ru/download/arccvid/pad.wmv