Jump to content

Gipsy

Members
  • Posts

    24
  • Joined

  • Last visited

1 Follower

About Gipsy

  • Birthday 12/29/2020

Personal Information

  • Flight Simulators
    DCS, MSFS
  • Location
    Portugal
  • Interests
    Aviation

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Massive update, much appreciated. I'me very glad that Museu do Ar - which is property of the Portuguese Air Force - could give you this kind of opportunity, sometimes we portuguese tend to be a bit bureucratic and closed minded for these kind of things. I've seen these beasts in static display many times, can't wait to fly it in DCS. Lastely, she's so ugly...I love it!
  2. Well, you have the For Sale Forum. Depending on the price and where you are based there will be interest for sure. Good luck.
  3. Well I guess that we are treating this subject as if it was the begining of something rather than an evolution of something. This is not a "good start" (like you wrote), this is a good evolution of DCS, let us not forget that we have a fairly recent build regarding MT, which cater to your needs in regards of servicing the whole community. Some priorities have to taken into account and NVidia has a good amount of the pie in regards of GPU. Like Hiob stated FSR is not of the table, we just don't know whats next, the only thing we know is that this step was revealed some months ago. I mean, they told it was coming, it's not a surprise...
  4. Yeah, so the tittle is pretty misleading. In a time of the year where is more common to hear about the new projects that teams are working on, reading a title like this one gives you a false sense that this is an actual project. I agree with what njoyyoursalad said, I think that effort should be made to bring us parts of the globe that aren't already avaiable. And like Silver_Dragon mentioned, the maps is ED's responsability, not Ugra.
  5. To be fair he did say that there were 4 announcements in queue, our minds just filled the blanks with what we wanted to read.
  6. Great initiative! Really shows your willingness to reach to your audience. For me it would be (in order of preference); AW-129 Mangusta, F-84F or G and F-105. But I got say that I completely agree with this:
  7. Usually, following the information that Nineline and BIGNEWY provided for other cases, it all depends on the 3rd party. When they are up to it they request their own subforum and ED provides. So, for now... We'll have to wait.
  8. Apparently Anubis is part of the team, altough it is unclear (as it should, I guess) the exact dev work he is on. Some resumed info:
  9. Jesus Christ man. Are you not confortable with the idea of your costumers sleeping well at night?
  10. By the looks of it, the C130 must be in an advance state, being the subject of a teaser. I can't recall one aircraft that had the announcement of its birth alongside with a teaser on ED's YT channel. I am ready to throw my money at you Airplane Simulation Company!!! There couldn’t be a more iconic heavy to start us with. Bring it on.
  11. Thanks for the reply! So, I guess, that's just the way it is and no way around it. Maybe, down the line, ED can make all the toggles in the Hind have a toggle-like structure.
  12. Hey, First of all I would like to thank all the users that benevolently come here to help out other users. It is much appreciated and I've learned a lot. (I posted this same text in this topic, but I really intended to post here) I am in the process of building some panels for the MI-24 Hind and I came across some difficulties in assigning two toggle switches and respective covers bindings to my physical switches. I followed the useful help in this topic and for a row of 3 switches and covers, I have this edited in the default lua file: {down = weapon_commands.Pilot_EMERG_RELEASE_COVER_Ext, pressed = weapon_commands.Pilot_EMERG_RELEASE_Ext, up = weapon_commands.Pilot_EMERG_RELEASE_COVER_Ext, cockpit_device_id = devices.WEAP_SYS, value_down = 1, value_pressed = 1, value_up = 0, name = _('Pilot Jettison Pylons Switch and Cover, UP/DOWN'), category = {_('Weapon Panel')}}, {down = weapon_commands.Pilot_EMERG_RELEASE_PU_COVER_Ext, pressed = weapon_commands.Pilot_EMERG_RELEASE_PU_Ext, up = weapon_commands.Pilot_EMERG_RELEASE_PU_COVER_Ext, cockpit_device_id = devices.WEAP_SYS, value_down = 1, value_pressed = 1 value_up = 0, name = _('Pilot Jettison Launcher Switch and Cover, UP/DOWN'), category = {_('Weapon Panel')}}, {down = weapon_commands.Pilot_EMERG_EXPLODE_COVER_Ext, pressed = weapon_commands.Pilot_EMERG_EXPLODE, up = weapon_commands.Pilot_EMERG_EXPLODE_COVER_Ext, cockpit_device_id = devices.WEAP_SYS, value_down = 1, value_pressed = 1, value_up = 0, name = _('Pilot Explosion on Jettison Switch and Cover, UP/DOWN'), category = {_('Weapon Panel')}}, One of the switches (the third line of code) works flawlessly. It's perfect, my physical switch goes up and in the sim, the cover goes up followed by the switch. The other two don't work, even if it all appears normal and equal as the previous. My physical switch is activated and the sim cover goes up, but the sim switch goes berserk and just flicks on and off really fast, without stopping. Any thoughts? They are connected through a Bodnar Board, BBI-32, and I've tested the switches in other bindings and they work as intended. Thanks
  13. Hey, First of all I would like to thank all the users that benevolently come here to help out other users. It is much appreciated and I've learned a lot. I am in the process of building some panels for the MI-24 Hind and I came across some difficulties in assigning two toggle switches and respective covers bindings to my physical switches. I followed the useful help in this topic and for a row of 3 switches and covers, I have this edited in the default lua file: {down = weapon_commands.Pilot_EMERG_RELEASE_COVER_Ext, pressed = weapon_commands.Pilot_EMERG_RELEASE_Ext, up = weapon_commands.Pilot_EMERG_RELEASE_COVER_Ext, cockpit_device_id = devices.WEAP_SYS, value_down = 1, value_pressed = 1, value_up = 0, name = _('Pilot Jettison Pylons Switch and Cover, UP/DOWN'), category = {_('Weapon Panel')}}, {down = weapon_commands.Pilot_EMERG_RELEASE_PU_COVER_Ext, pressed = weapon_commands.Pilot_EMERG_RELEASE_PU_Ext, up = weapon_commands.Pilot_EMERG_RELEASE_PU_COVER_Ext, cockpit_device_id = devices.WEAP_SYS, value_down = 1, value_pressed = 1 value_up = 0, name = _('Pilot Jettison Launcher Switch and Cover, UP/DOWN'), category = {_('Weapon Panel')}}, {down = weapon_commands.Pilot_EMERG_EXPLODE_COVER_Ext, pressed = weapon_commands.Pilot_EMERG_EXPLODE, up = weapon_commands.Pilot_EMERG_EXPLODE_COVER_Ext, cockpit_device_id = devices.WEAP_SYS, value_down = 1, value_pressed = 1, value_up = 0, name = _('Pilot Explosion on Jettison Switch and Cover, UP/DOWN'), category = {_('Weapon Panel')}}, One of the switches (the third line of code) works flawlessly. It's perfect, my physical switch goes up and in the sim, the cover goes up followed by the switch. The other two don't work, even if it all appears normal and equal as the previous. My physical switch is activated and the sim cover goes up, but the sim switch goes berserk and just flicks on and off really fast, without stopping. Any thoughts? They are connected through a Bodnar Board, BBI-32, and I've tested the switches in other bindings and they work as intended. Thanks
  14. Hi Mikhail, Please add me to the list. Shipping to Lisbon - Portugal. Thanks!
×
×
  • Create New...