Jump to content

ASET Avionics Pack v 2.1 (for the modders who create IVA)


alexustas

Recommended Posts

@MrFancyPL

It is required to add RasterPropMonitorComputer module in your part config

MODULE 
		{
			name = RasterPropMonitorComputer
			storedStrings = v 2.0.0.0|26.12.2016|    MK1-Cockpit    |  MK-1 ||ASET-A1|MK1|     SQUAD & A.S.E.T.
			// = (0)<version> |(1) <date> |(2) <name for MFD STBY screen & Flight Books. 18 char max>| (3,4)<full name (2 lines)> |(5) < version of flight books, manuals...>|(6) <short name> |(7) Company
			triggeredEvents = ASET_AUTOBRAKE|ASET_AUTOSPOILER|ALCOR_CALLRECOVERYTEAM
			
			RPM_COLOROVERRIDE
			{
			
			// push buttons backlight
			
				COLORDEFINITION
				{			
					name = ASET_PUSHBUTTON_BACKLIGHT_ACTIVECOLOR
					color= 110,155,110,255
				}			
			// switchers
			
				COLORDEFINITION
				{
					name = ASET_SWITCHER_NAME_POSITIVECOLOR
					color= 80,255,50,255
				}
				COLORDEFINITION
				{
					name = ASET_SWITCHER_STATE_POSITIVECOLOR
					color= 160,255,0,255
				}
				COLORDEFINITION
				{
					name = ASET_SWITCHER_BORDER_POSITIVECOLOR
					color= 10,50,10,255
				}
				COLORDEFINITION
				{
					name = ASET_SWITCHER_MARK_POSITIVECOLOR
					color= 255,155,20,255
				}
							
			// LEDs off
			
				COLORDEFINITION
				{
					name = ASET_SWITCHER_LEDS_POSITIVECOLOR
					color= 0,200,0,255
				}
				COLORDEFINITION
				{
					name = ASET_SWITCHER_LEDS_ZEROCOLOR
					color= 50,50,50,255
				}
			// Numeric Input display
			
			// background
			
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_DIFFUSE_ACTIVECOLOR
					color= 0,0,0,255
				}
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_DIFFUSE_PASSIVECOLOR
					color= 50,30,0,255
				}
				
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_EMISSIVE_ACTIVECOLOR
					color= 50,30,0,255
				}
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_EMISSIVE_PASSIVECOLOR
					color= 0,0,0,255
				}
				
			// readout
			
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_POSITIVECOLOR
					color= 255,85,0,255
				}
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_ZEROCOLOR
					color= 130,35,0,255
				}
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_NEGATIVECOLOR 
					color= 0,0,0,0
				}
				COLORDEFINITION
				{
					name = ASET_NUMINPUT_DISPLAY_GHOSTCOLOR
					color= 85,35,0,80
				}	
			// label plate 
			
			// background
				
				COLORDEFINITION
				{
					name = ASET_PLATEBKG_DIFFUSE_PASSIVECOLOR
					color= 130,130,130,255
				}
				COLORDEFINITION
				{
					name = ASET_PLATEBKG_DIFFUSE_ACTIVECOLOR
					color= 130,130,130,255
				}
				
				COLORDEFINITION
				{
					name = ASET_PLATEBKG_EMISSIVE_PASSIVECOLOR
					color= 0,0,0,255
				}
				COLORDEFINITION
				{
					name = ASET_PLATEBKG_EMISSIVE_ACTIVECOLOR
					color= 0,0,0,255
				}
				
			// label text
				
				COLORDEFINITION
				{
					name = ASET_PLATETEXT_POSITIVECOLOR
					color= 80,230,10,255
				}
				COLORDEFINITION
				{
					name = ASET_PLATETEXT_ZEROCOLOR
					color= 255,255,255,255
				}	
				
			// panel lines
				
				COLORDEFINITION
				{
					name = ASET_PANELDIVIDER_PRIMARY_BACKLIGHTCOLOR
					color= 50,100,10,255
				}	
				
			}
		}

You can edit the values of 'storedStrings' and color definitions as you need

Link to comment
Share on other sites

21 minutes ago, MrFancyPL said:

I'm sorry but i don't know what I am doing wrong. I put that module into config of cockpit and nothing happened.

you need to put this in the config of  the PART, not in the internal config

text should appear on the "Stand by" screen of MFD.
On screenshots above, I can only see the blue lines without text, indicating the lack of the "
RasterPropMonitorComputer" module in the part cfg

Edited by alexustas
Link to comment
Share on other sites

@MrFancyPL

2 hours ago, MrFancyPL said:

Hello, can somone help me ? I have got problem with gauges from ASET avionics pack. I don't know why they are glowing with the purple color. It looks very annoying. Can someone tell me how to fix it ?

955sZX1.png

XMqCzGV.png

It seems I'm confused. you are creating this mod or you just use them?

Link to comment
Share on other sites

24 minutes ago, MrFancyPL said:

RlKexm2.png

 

1 minute ago, MrFancyPL said:

I have ASET_props 1.4 and ASET Avionics 2.0 installed

Design of warning lights ("LOW ALT", 'LOW FUEL" etc) indicates to me that you have an older version of props

Link to comment
Share on other sites

21 hours ago, Ser said:

@alexustas, thanks, I'll try that.

Have you thought of the following: what if procedures from charts (approach, landing) were specified as cfg's? That would allow a great scalability, here is what I mean:
Flying around KSC is cool but there are plenty of custom runways that a player can add in his game.
1. Using the data from cfg's the charts could be generated procedurally. I doubt that anyone would be patient enough to force all those custom runway creators to draw proper charts and maintain them but having them procedurally generated we could have default charts even for the laziest ones.
2. Those data could be used by an ATC mod for vectoring, landing etc., thus we'd automatically had both charts and ATC services using the same data, and for every custom runway added.

Are you interested in that?

@Ser

implementation of navigation using RPM - is a real tricky hack. So features that you have to offer, there is no sense to discuss for now.

BUT.  when @MOARdV release its magnificent mod MAS, we can talk about this more substantively.

Edited by alexustas
Link to comment
Share on other sites

@Ser

At first. thank you very much for your feedback about navigation. in fact it is the first effective response on this feature for all time

 

On 10.02.2017 at 1:54 PM, Ser said:

I've tuned to IKW at 45 km distance and pushed "IDENT" but no morse code was audible. ADF and DME worked but the code became audible only at the very moment when the glide slope was intercepted at about 10 km. Is that intended?

No. You should hear the Morse call sign, when you have capture localizer.

capturing condition following:

  • distance < 30 km from TDZ
  • you must be in the beam cone +/- 17,5 deg
  • altitude < 4000 m (ASL)
  • HSI should be set on a course 90 for 09 rwy  (or 270 for 27 rwy)

"LOC" mark should appear on 'NAV 1' radio

 

3. On the page 4-2 of the chart (KKSC landing) there's a fix BAKOR (id SCE) marked as NDB with its own MW frequency. Base and final turn points of the circuit reference to SCE but I couldn't find a way to tune to that MW frequency as both NAV radios are VHF. How should that be done?

You have the ability to configure both radios on the NDB station. Use the "STEP" button to quickly change the frequency

 

 

@linuxgurugamer

31 minutes ago, linuxgurugamer said:

Comment on the ckan stuff:

notice that ASETAvionics has 2 distinct "parts" within it. The ClassicPack and the ModernPack, should these be split or do they belong together?

No. there is no need to separate these packs

 

 

 

Edited by alexustas
Link to comment
Share on other sites

Looks like it.

@alexustas, comparing the files to what we were getting ready to release as a CE edition,I see that the following are missing (not a complete list):

  • MK1-2_InternalsASET
  • LanderCabinSmall_InternalASET
  • ExtCamRadialVert
  • ASET_LandingLegs (we had a modified config to make it work)
  • ALCOR_IVA_Patch
Link to comment
Share on other sites

@linuxgurugamer what is the "CE edition"?

I decided to rename the some  folders for more clarity. because it was a complete mess.

  • MK1-2_InternalsASET -> MK1-2_IVA_Replacement_by_ASET
  • LanderCabinSmall_InternalASET -> Mk1_Lander_Can_IVA_Replacement_by_ASET
  • ExtCamRadialVert -> ASET/ExtCamRadialVert
  • ASET_LandingLegs (we had a modified config to make it work)
  • ALCOR_IVA_Patch -> ALCOR_Advanced_IVA

I assume this has created some problems? if so, I am very sorry about this. I do not understand how the CKAN works

Edited by alexustas
Link to comment
Share on other sites

1 hour ago, alexustas said:

@linuxgurugamer what is the "CE edition"?

I decided to rename the some  folders for more clarity. because it was a complete mess.

  • MK1-2_InternalsASET -> MK1-2_IVA_Replacement_by_ASET
  • LanderCabinSmall_InternalASET -> Mk1_Lander_Can_IVA_Replacement_by_ASET
  • ExtCamRadialVert -> ALCOR_Advanced_IVA/ExtCamRadialVert
  • ASET_LandingLegs (we had a modified config to make it work)
  • ALCOR_IVA_Patch -> ALCOR_Advanced_IVA

I assume this has created some problems? if so, I am very sorry about this. I do not understand how the CKAN works

A copy of the mod released by someone else, it has since been deleted.

When did you rename the folders?  Before the release?

2 hours ago, linuxgurugamer said:

Looks like it.

@alexustas, comparing the files to what we were getting ready to release as a CE edition,I see that the following are missing (not a complete list):

  • MK1-2_InternalsASET
  • LanderCabinSmall_InternalASET
  • ExtCamRadialVert
  • ASET_LandingLegs (we had a modified config to make it work)
  • ALCOR_IVA_Patch

@alexustas, I actually looked in what was installed, i didn't see these at all

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...