20161
Combat Warplanes / Re: Four new F-16 for Poland
« on: December 23, 2006, 10:42:48 AM »
Well well well- it is an politics and better not to continue topic in that direction. But you are right PV Chairman 
News:
Forum is closed for new members. All content is private and can not be shared
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
20162
Combat Warplanes / Re: Impeller
« on: December 23, 2006, 10:41:32 AM »
God bless you Italian friend 
20163
Warplane Art / Re: Srpska Avijatika is coming home
« on: December 23, 2006, 10:38:52 AM »
Yes there is solution but no time in the moment- I will prepare answer in few day's... I hope
20164
Combat Warplanes / Re: Impeller
« on: December 22, 2006, 10:49:54 PM »
It is a bit stronger... 80 or up to 120... maybe. This air cooled engine in that time was not so strong. Santiono- help please
20165
Combat Warplanes / Re: Syntetic fuel test
« on: December 22, 2006, 10:48:07 PM »
Greetings friend- very good update to this very hot topic
20166
Warplane Art / Re: Speed road to Photoshop
« on: December 22, 2006, 05:18:52 PM »
Photoshop offer to you all on your finger tips and much of the action can be taken from the keyboard. As much as you learn shortcuts, that much you will make faster your work.
Here it is first tip- how to find out how much is our image large. You can go to Image- Image size but there is short way- hold Ctrl-Alt and press I and you will see dialog as attached here. You can see there size in pixels, document print size as well document resolution. If you want to see canvas size you just hold Ctrl-Alt and press C.
Here it is first tip- how to find out how much is our image large. You can go to Image- Image size but there is short way- hold Ctrl-Alt and press I and you will see dialog as attached here. You can see there size in pixels, document print size as well document resolution. If you want to see canvas size you just hold Ctrl-Alt and press C.
20167
Combat Warplanes / Re: Impeller
« on: December 22, 2006, 01:57:21 PM »
Early attempt to develop some kind of jet propulsive system but far from real jet.
20168
Let Let Let Announcment / Re: Happy Holidays
« on: December 22, 2006, 01:56:15 PM »
Most beautiful greetings I have seen!!! Thank you friend
20169
Combat Warplanes / Re: Impeller
« on: December 22, 2006, 11:55:41 AM »
Brilliant imagesd Santino 
And gentlemen from Australia rebuilt preserved sample or built completely new one 
And gentlemen from Australia rebuilt preserved sample or built completely new one
20172
Warplane Art / Re: Srpska Avijatika is coming home
« on: December 21, 2006, 12:01:08 AM »
Hey crew- I have to introduce to you the man to who I grant all my knowledge about the Photoshop- divanov!!!
Under the pallete for brushes you have various shapes and some are good for vawes and some good for plants. I use few types in various settings for the grass, different type for three and sky and clouds are special story.
Thank you for your comment
Under the pallete for brushes you have various shapes and some are good for vawes and some good for plants. I use few types in various settings for the grass, different type for three and sky and clouds are special story.
Thank you for your comment
20173
Combat Warplanes / KC-135 accident
« on: December 20, 2006, 06:35:36 PM »
PRESS RELEASE -- Secretary of the Air Force, Office of Public Affairs
Release No. 051206
December 19,2006
KC-135 ACCIDENT INVESTIGATION BOARD COMPLETE
SCOTT AIR FORCE BASE, Ill. - Air Mobility Command today released the results of its investigation into the Sept. 26 KC-135R aircraft accident at Manas International Airport, Bishkek, Kyrgyz Republic.
The collision between the TU-154 and KC-135R aircraft was clearly an accident and not the result of any intentional conduct. The Accident Investigation Board, convened by AMC, determined that the accident was caused by the Kyrgyzaeronavigation air traffic controller who cleared a civilian airliner for takeoff without verifying that the KC-135R was clear of the runway. In addition to the air traffic controller, the AIB found evidence of several contributing factors involving the KC-135R aircrew, conflicting published airport notices, and a tower liaison employed by the U.S. Government to facilitate communication between the tower and U.S. aircrews. Although the AIB found the air traffic controller primarily at fault, the U.S. KC-135R crew and tower liaison shared responsibility for ensuring the KC-135R cleared the runway to a safe location following landing. The accident might have been avoided had any of them exercised better awareness of their situation.
On Sept. 26, at approximately 8:03 p.m. local time, a KC-135R landed at Manas International Airport following a combat mission over Afghanistan. After landing, the KC-135R was parked at the intersection of the active runway and a taxiway while the crew awaited clarification on instructions from the air traffic control tower. The KC-135R was struck by a host nation TU-154 that was taking off. The TU-154's right wing struck the fairing of the KC-135R's No. 1 engine. The force of the impact nearly severed the No. 1 engine from KC-135R and destroyed a portion of the aircraft's left wing. The TU-154 lost approximately six feet of its right wingtip, but was able to get airborne and return to the airport for an emergency landing with no additional damage to the aircraft.
The three aircrew members on board the KC-135R, as well as the nine aircrew members and 52 passengers aboard the TU-154, survived the accident. None of the aircrew or passengers onboard the TU-154 sustained any injuries. One KC-135 crewmember sustained minor abrasions while evacuating the aircraft.
The primary purpose of the AIB was to provide a publicly releasable report of the facts and circumstances surrounding the accident. Although the AIB determined the principal cause of the mishap was the Kyrgyzaeronavigation controller clearing the TU-154 for takeoff without verifying that KC-135R was clear of the runway, there was evidence the following factors also contributed to the mishap:
- The Kyrgyz air traffic controller's instruction to vacate at taxiway Golf after dark conflicted with a published Notice to Airmen (NOTAM) that limited that taxiway's use to daylight hours. The contractor safety liaison (LNO) employed by the U.S. Air Force to facilitate communication between its aircrews and Kyrgyz controllers did not clarify the apparent discrepancy.
- After questioning the Kyrgyz controller's instruction to vacate the runway at taxiway Golf, the LNO instructed the KC-135R crew to hold short of Alpha. The mishap KC-135R crew misperceived the LNO's instructions and responded "holding short of Golf." The LNO failed to catch the read-back error.
- The Kyrgyz controller failed to maintain awareness of the KC-135R's location.
- The LNO failed to maintain situational awareness and intervene when the controller's actions endangered the KC-135R and aircrew.
The KC-135R is assigned to the 92nd Air Refueling Wing, Fairchild Air Force Base, Wash. While deployed at Manas AB, the KC-135R and its aircrew were assigned to U.S. Central Command's 376th Air Expeditionary Wing, flying missions supporting coalition aircraft over Afghanistan.
For more information contact Air Mobility Command Public Affairs at (618) 229-7843.
Release No. 051206
December 19,2006
KC-135 ACCIDENT INVESTIGATION BOARD COMPLETE
SCOTT AIR FORCE BASE, Ill. - Air Mobility Command today released the results of its investigation into the Sept. 26 KC-135R aircraft accident at Manas International Airport, Bishkek, Kyrgyz Republic.
The collision between the TU-154 and KC-135R aircraft was clearly an accident and not the result of any intentional conduct. The Accident Investigation Board, convened by AMC, determined that the accident was caused by the Kyrgyzaeronavigation air traffic controller who cleared a civilian airliner for takeoff without verifying that the KC-135R was clear of the runway. In addition to the air traffic controller, the AIB found evidence of several contributing factors involving the KC-135R aircrew, conflicting published airport notices, and a tower liaison employed by the U.S. Government to facilitate communication between the tower and U.S. aircrews. Although the AIB found the air traffic controller primarily at fault, the U.S. KC-135R crew and tower liaison shared responsibility for ensuring the KC-135R cleared the runway to a safe location following landing. The accident might have been avoided had any of them exercised better awareness of their situation.
On Sept. 26, at approximately 8:03 p.m. local time, a KC-135R landed at Manas International Airport following a combat mission over Afghanistan. After landing, the KC-135R was parked at the intersection of the active runway and a taxiway while the crew awaited clarification on instructions from the air traffic control tower. The KC-135R was struck by a host nation TU-154 that was taking off. The TU-154's right wing struck the fairing of the KC-135R's No. 1 engine. The force of the impact nearly severed the No. 1 engine from KC-135R and destroyed a portion of the aircraft's left wing. The TU-154 lost approximately six feet of its right wingtip, but was able to get airborne and return to the airport for an emergency landing with no additional damage to the aircraft.
The three aircrew members on board the KC-135R, as well as the nine aircrew members and 52 passengers aboard the TU-154, survived the accident. None of the aircrew or passengers onboard the TU-154 sustained any injuries. One KC-135 crewmember sustained minor abrasions while evacuating the aircraft.
The primary purpose of the AIB was to provide a publicly releasable report of the facts and circumstances surrounding the accident. Although the AIB determined the principal cause of the mishap was the Kyrgyzaeronavigation controller clearing the TU-154 for takeoff without verifying that KC-135R was clear of the runway, there was evidence the following factors also contributed to the mishap:
- The Kyrgyz air traffic controller's instruction to vacate at taxiway Golf after dark conflicted with a published Notice to Airmen (NOTAM) that limited that taxiway's use to daylight hours. The contractor safety liaison (LNO) employed by the U.S. Air Force to facilitate communication between its aircrews and Kyrgyz controllers did not clarify the apparent discrepancy.
- After questioning the Kyrgyz controller's instruction to vacate the runway at taxiway Golf, the LNO instructed the KC-135R crew to hold short of Alpha. The mishap KC-135R crew misperceived the LNO's instructions and responded "holding short of Golf." The LNO failed to catch the read-back error.
- The Kyrgyz controller failed to maintain awareness of the KC-135R's location.
- The LNO failed to maintain situational awareness and intervene when the controller's actions endangered the KC-135R and aircrew.
The KC-135R is assigned to the 92nd Air Refueling Wing, Fairchild Air Force Base, Wash. While deployed at Manas AB, the KC-135R and its aircrew were assigned to U.S. Central Command's 376th Air Expeditionary Wing, flying missions supporting coalition aircraft over Afghanistan.
For more information contact Air Mobility Command Public Affairs at (618) 229-7843.
20174
Warplane Art / Re: Srb Historical markings review
« on: December 20, 2006, 06:26:38 PM »
Excellent installment for all those who want to have general overview on the Serbian/Yugoslav national insignia used on warplanes. Greetings!!
20175
Warplane Art / Re: Speed road to Photoshop
« on: December 20, 2006, 06:23:49 PM »
Most important when you instal Photoshop is to make clear determination how this program have to work. First go to the Edit- Preferences- General.
Under the General keep all what you see but you can make some changes in the History States. By the default it is 20 states but if you want to keep memory you should reduce this number. But also if you have no problem with memory you can increase this number on eg. 30 states. This present how many back step Photoshop remember and this will use in the History panel later.
Next is File handling and leave it as it is.
Display and Cursors leave as it is.
Transparency & Gamut also leave as it is.
Units and Rulers- I put the Rulers on milimeters [ mm] and type in points. I use metric measurement but there is also inches. No need to take other measurements for Type [this is the size of text] as well all use measure in points. Also no need to make any change on Print Resolution and Screen Resolution.
Next step is Guides, Grid & Slices and also leave as it is.
Plug-Ins & Scratch Disks is very important and go down on the area for the scratch disc. This determinate where the Photoshop should put additional data and store memory during the work. You have present as much disc as much you have it on hard disc. As well I have it four I see there four disc. Never- never- never put the first scratch on disc "C" even if you have there most space. First disc have to be the one with most space and then the rest with smaller and smaller space and the last one is the "C".
Next is the Memory & Image Cashe. Lets be clear- don't instal Photoshop CS2 if you have no at least 1 GB of RAM!!! Some under the 250 MB is used by the system and rest can be used by Photoshop. Photoshop find its brutal power in the RAM memory, you can have most expencive graphic card in the world it's worth nothing if you have no RAM. Best chice is the Dual Chanell RAM of some 2 GB... my dream Well I have set there 85% of available RAM for Photoshop and I work smooth.
Type leave as it is.
And after this finished you can start with Photoshop actions...
Under the General keep all what you see but you can make some changes in the History States. By the default it is 20 states but if you want to keep memory you should reduce this number. But also if you have no problem with memory you can increase this number on eg. 30 states. This present how many back step Photoshop remember and this will use in the History panel later.
Next is File handling and leave it as it is.
Display and Cursors leave as it is.
Transparency & Gamut also leave as it is.
Units and Rulers- I put the Rulers on milimeters [ mm] and type in points. I use metric measurement but there is also inches. No need to take other measurements for Type [this is the size of text] as well all use measure in points. Also no need to make any change on Print Resolution and Screen Resolution.
Next step is Guides, Grid & Slices and also leave as it is.
Plug-Ins & Scratch Disks is very important and go down on the area for the scratch disc. This determinate where the Photoshop should put additional data and store memory during the work. You have present as much disc as much you have it on hard disc. As well I have it four I see there four disc. Never- never- never put the first scratch on disc "C" even if you have there most space. First disc have to be the one with most space and then the rest with smaller and smaller space and the last one is the "C".
Next is the Memory & Image Cashe. Lets be clear- don't instal Photoshop CS2 if you have no at least 1 GB of RAM!!! Some under the 250 MB is used by the system and rest can be used by Photoshop. Photoshop find its brutal power in the RAM memory, you can have most expencive graphic card in the world it's worth nothing if you have no RAM. Best chice is the Dual Chanell RAM of some 2 GB... my dream
Well I have set there 85% of available RAM for Photoshop and I work smooth.Type leave as it is.
And after this finished you can start with Photoshop actions...