Jump to content

Archived

This topic is now archived and is closed to further replies.

abdelsa

pmdg 777 vc light problem

Recommended Posts

Hm, I noticed the same thing yesterday! Any ideas?


Ivan Majetic

MAXIMUS X HERO, i7 8086k 5,0 Ghz, NZXT KRAKEN Z73, ASUS STRIX GTX1080Ti OC, G.SKILL TridentZ DDR4 32 Gb, WD HDD 2TB, SAMSUNG 840PRO, SAMSUNG 850EVO, SAMSUNG 970EVO Plus, ASUS PG348Q

Share this post


Link to post

I had this as well. I had used the DX10 toolbox to turn VC shadows on for the 777 a long time ago. After installing the latest SP1C I observed this as well. I went in and deleted the modified VC model file within both the -200 and -300 and reran the SP1C installers. Then I reran the DX10 toolbox and clicked to add VC shadows. This fixed the problem that is in the OP's post. However I do not have VC shadows anymore. Sucks... I think PMDG updated something in the model file and now we can no longer get VC shadows.....


Eric 

 

 

Share this post


Link to post

Eric, shadows work here. Skip any work with the toolbox and just go with the setting in your fsx.cfg as explained here. http://forum.avsim.net/topic/454014-new-fsx-setting-in-fsxcfg-for-dx10-forcevcshadowmap/

 

No need to touch any model files anymore. "Force VCWalls" might help on some occasions.

 

As for the clock area at night, I would have to check if I get the same error. Edited. I've just checked and I don't see the clock area coming up differently than the rest. Can not confirm the error for the -200 and -300.

Share this post


Link to post

Eric, shadows work here. Skip any work with the toolbox and just go with the setting in your fsx.cfg as explained here. http://forum.avsim.net/topic/454014-new-fsx-setting-in-fsxcfg-for-dx10-forcevcshadowmap/

 

No need to touch any model files anymore. "Force VCWalls" might help on some occasions.

 

As for the clock area at night, I would have to check if I get the same error. Edited. I've just checked and I don't see the clock area coming up differently than the rest. Can not confirm the error for the -200 and -300.

Yep, I skipped the tool box and added that line in the fsx.cfg as well. I see the shadows on the glare shield and on the front pillars. I used to have it all over the cockpit but that is no longer the case for some reason?? I have Force VC Walls checked as well....very odd..


Eric 

 

 

Share this post


Link to post

Needless to say that, if PMDG ever decided to patch out the ability to receive cockpit shadows in DX10, I would be very.. disappointed.

 

Forgot to say. I shall check my settings later to maybe help on discovering what could prevent "full" shadows for you.

 

Second edit. Posting the settings and the VC pic. Please check if the issue stems from the sun's angle. I used an early summer day in Seattle not a noon situation.

 

g5OZoQl.jpg

 

ovVOzOX.jpg

 

Don't mind the green pointers in the pic. Those are from my XPOI addon and help me finding my way with GA planes. The 777 is a GA plane, right? :lol:

 

And finally. We have to admit that we've hijacked the thread since we are no longer on the clock area issue. :blush: But I shall post another picture at night, so that one can see the clock area being lit as expected.

 

Both are from the -200, the last one with the flood light (for the Captain's side) on.

 

l8nFcyy.jpg

 

tn1L0iX.jpg

Share this post


Link to post

The clock area was working fine for me until I installed FSCrew for the 777. Now I get it like the OP posted.


Eric 

 

 

Share this post


Link to post

Good observation then. Is FS2Crew placing a clickspot or something in that area? I don't have it.

Share this post


Link to post

I solved the digital clock area anomally with reinstalling SP1c.


Ivan Majetic

MAXIMUS X HERO, i7 8086k 5,0 Ghz, NZXT KRAKEN Z73, ASUS STRIX GTX1080Ti OC, G.SKILL TridentZ DDR4 32 Gb, WD HDD 2TB, SAMSUNG 840PRO, SAMSUNG 850EVO, SAMSUNG 970EVO Plus, ASUS PG348Q

Share this post


Link to post

I solved the digital clock area anomally with reinstalling SP1c.

 

I did too. Then I installed FSCrew and its back to being how it was.....color is now much lighter at night.


Eric 

 

 

Share this post


Link to post
At least we know the problem lies within the FS2Crew

 

I did too. Then I installed FSCrew and its back to being how it was.....color is now much lighter at night.

 


Ivan Majetic

MAXIMUS X HERO, i7 8086k 5,0 Ghz, NZXT KRAKEN Z73, ASUS STRIX GTX1080Ti OC, G.SKILL TridentZ DDR4 32 Gb, WD HDD 2TB, SAMSUNG 840PRO, SAMSUNG 850EVO, SAMSUNG 970EVO Plus, ASUS PG348Q

Share this post


Link to post

I've FS2Crew too... so maybe that's the problem. Don't know how to fix it anyway...


Abdel Sotolongo Abella

fs2crew_747_banner1.png

Share this post


Link to post

I think FS2Crew is the likely cause. I don't have it installed and use DX10 and have never noticed this issue. I'm guessing its the addition of a click spot to start FS2Crew that is causing the issue.


 

 

                                                                                                                                                        

Share this post


Link to post

FS2Crew 777 does not use a clickspot to open the box, it's a key assignement.

 

Stephane


vpa055.png

Location : FMEE

Share this post


Link to post
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    33%
    $8,485.00 of $25,000.00 Donate Now
×
×
  • Create New...