wulfbindewald Posted February 8, 2015 Share Posted February 8, 2015 Hi there, the chimney smoke of the two cabins in front of RWY08 is flashing or is completly surpressed when using DX10 during dawn independent of the PAJN ORBX control panel check box set to DX9 or DX10. At day the smoke is visible and fine. SteveFX (dev from DX10 fixer) could not find a rational and satisfactory workaround for this prob. Any chance to get it solved? An intermediate solution is to switch on the aircraft landing lights, but it is not really the preferred solution. Wulf Link to comment Share on other sites More sharing options...
Holger Sandmann Posted February 8, 2015 Share Posted February 8, 2015 Hi Wulf, interesting though I've no idea about the cause or a fix. The smoke effects for our rustic cabins are actually part of the model (via an effect attachment point that calls the default fx_ChimneySmoke.fx) meaning there's nothing we can control externally other than placing (or deleting) the cabin. Cheers, Holger Link to comment Share on other sites More sharing options...
jaydor Posted February 8, 2015 Share Posted February 8, 2015 Have you got the animations box ticked in settings? Link to comment Share on other sites More sharing options...
wulfbindewald Posted February 9, 2015 Author Share Posted February 9, 2015 Hi Holger, thanks for your info. Please consider this thread as closed. Further improvement with respect to this specific DX10 related issue will be tried together with SteveFX. Have you got the animations box ticked in settings? If the "animation box" is located in the FSX menu....nearly all scenery sliders are maxed with exception to 5m res. Wulf Link to comment Share on other sites More sharing options...
John Dow Posted February 10, 2015 Share Posted February 10, 2015 Just to add something... I've noticed some texture items flashing on and off in DX10 when I'm really hammering the system, eg the road lights in Canberra Cityscape with everything set to max. So maybe this is related? Link to comment Share on other sites More sharing options...
Nick Cooper Posted February 13, 2015 Share Posted February 13, 2015 I found today that in FSX-SE Dx10, chimney smoke effects flashed with the aircraft beacon until I ran the effects converter, including particle effects which are excluded by default. You could try that perhaps, if you haven't already. Link to comment Share on other sites More sharing options...
wulfbindewald Posted February 14, 2015 Author Share Posted February 14, 2015 I found today that in FSX-SE Dx10, chimney smoke effects flashed with the aircraft beacon until I ran the effects converter, including particle effects which are excluded by default. You could try that perhaps, if you haven't already. Thanks. Yes, this solves the smoke flashing but then the PAPI lights are off. Only switching the AC landing lights on "corrects" this. Hopefully SteveFX will find a workaround in the future. I´ll keep this forum informed. Wulf Link to comment Share on other sites More sharing options...
Stevefsx Posted March 7, 2015 Share Posted March 7, 2015 The underlying problem is the fsx dx10 effects system! when optimising effects it appears to leak properties from one effect to the next until a two effect texture changes have occurred. In this case the problem is the flashing property which the approach lights have in fx_HS_FSX_SAK_PAJN_LDIN_D.fx. This effect contains a single texture change. This flashing property leaks to the shack's chimney smoke effect which must be next in the sort order. If you remove the shacks the flashing instead gets passed to the street lights. The best workaround is to add an extra (20th) emitter into LDIN_D that displays a non flashing black (invisible ) light using a different texture to the preceding strobes. This extra texture change in LDIN_D is sufficent to prevent the flashing property being passed on. Link to comment Share on other sites More sharing options...
Holger Sandmann Posted March 7, 2015 Share Posted March 7, 2015 Hi Steve, nice bit of sleuthing, many thanks for the explanation! If I read this correctly there's no way to predict this kind of unwanted interaction meaning one cannot avoid it up-front. I can make those changes to the effect file. Does "using a different texture" mean a completely separate texture file or just a different offset within the same sheet? (effect textures like fx_2.bmp contain more than one "sprite"). Cheers, Holger Link to comment Share on other sites More sharing options...
Stevefsx Posted March 8, 2015 Share Posted March 8, 2015 Holger Yes no way to predict really. It needs to be a different texture sheet to the preceding one but it can be one already used so I added this which uses fx_1.bmp again after the marine texture used for the strobes. [Emitter.20] Lifetime=0.50, 0.50 Delay=0.00, 0.00 Bounce=0.00 No Interpolate=1 Rate=1.00, 1.00 X Emitter Velocity=0.00, 0.00 Y Emitter Velocity=0.00, 0.00 Z Emitter Velocity=0.00, 0.00 Drag=0.00, 0.00 X Particle Velocity=0.00, 0.00 Y Particle Velocity=0.00, 0.00 Z Particle Velocity=0.00, 0.00 X Rotation=0.00, 0.00 Y Rotation=0.00, 0.00 Z Rotation=0.00, 0.00 X Offset=0.00, 0.00 Y Offset=0.00, 0.00 Z Offset=0.00, 0.00 [Particle.20] Lifetime=0.00, 0.00 Type=19 X Scale=0.30, 0.30 Y Scale=0.30, 0.30 Z Scale=0.00, 0.00 X Scale Rate=0.00, 0.00 Y Scale Rate=0.00, 0.00 Z Scale Rate=0.00, 0.00 Drag=0.00, 0.00 Color Rate=0.00, 0.00 X Offset=0.00, 0.00 Y Offset=0.00, 0.00 Z Offset=0.00, 0.00 Fade In=0.00, 0.00 Fade Out=0.00, 0.00 Rotation=0.00, 0.00 Face=1, 1, 1 [ParticleAttributes.20] Blend Mode=2 Texture=fx_1.bmp Bounce=0.00 Color Start=0, 0, 0, 1 Color End=0, 0, 0, 0 Jitter Distance=0.00 Jitter Time=0.00 uv1=0.00, 0.00 uv2=0.50, 0.50 X Scale Goal=0.00 Y Scale Goal=0.00 Z Scale Goal=0.00 Extrude Length=0.00 Extrude Pitch Max=0.00 Extrude Heading Max=0.00 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.