Welcome, Guest. Please Login or Register
YaBB - Yet another Bulletin Board
  Visit YaBB today Wink

FFDS Home | TIPS Section | Tutorials Section | Resources Section | Utilities Section

Military | FSDS | Jetliners | Real Planes Section | Gmax | Rotorcraft | Business | Civilian

  HomeHelpSearchLoginRegister  
 
 
Pages: 1 
Send Topic Print
DX10 (Read 7374 times)
28th Oct, 2010 at 12:47am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
It might be something that I have messed up (highly likely) but on my current project after compile the aircraft shows correctly in FSX under DX9 mode but in DX10 it appears all washed out as if the spec is overpowering the diffuse.
I have used more or less the same settings I used for my last project and that worked fine. The only difference is a newer version of Tweak. Has any body else used Tweak V2.81 and tested in DX10 mode yet? If ok it must be something I have done or ommited
Very very frustrating.
 
IP Logged
 
Reply #1 - 28th Oct, 2010 at 3:09am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
OK I decided after trying everything I could think of (took 10 mins  Grin) I decided to do a re-compile on one of my old models with the new tweak.
I did not change anything from the original KFG files and resored my old XML file.
On compile the new model displays a lot of differences in the textures regarding spec and bloom etc without any modification.
So this is either a bug or a new way of doing the textures must be found.
It seems that the whole settings are changed and values.
 
IP Logged
 
Reply #2 - 28th Oct, 2010 at 5:18am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
On further investigation the FSDSxTweak added spec and bloom to VC textures even when they were not specified in the KFG file on the original model. Strange Huh
I will go back a version or two and compile again to confirm my findings but I suspect it was the update from 2.8 to 2.81 that is causing the problem.
 
IP Logged
 
Reply #3 - 29th Oct, 2010 at 2:33am

DaveNunez   Offline
YaBB Moderator
Seattle, Washington

Gender: male
Posts: 504
*****
 
Thanks, the more info the better!

I do pre-populate by default some values which I believe are harmless, but hey, I don't run under DX10, so testing is rather limited!

Please let me know what you discover, so we can fix up the bugs as the appear.

 

Multimedia File Viewing and Clickable Links are available for Registered Members only!!  You need to Login or Register&&Multimedia File Viewing and Clickable Links are available for Registered Members only!!  You need to Login or Register
&&
IP Logged
 
Reply #4 - 29th Oct, 2010 at 3:05am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Hi DAVE,
Still not sure - but you know my setup always throws something up because of the compile sizes of the models. One thing I have done is switch back to V2.7 and this has made no difference. What is different on the earlier version compile is the appearance of the transparency materials so it could be something to do with the way the Alpha channels are processed - this might explain why the spec power in DX10 is overpowering the diffuse texture on the new version. I notice that with V2.81 the alpha channel on all textures has a greater effect. One other thing is if I edit the KFG file after compile it throws up all sorts of compile error messages regarding memory etc. I did a compile with the Mirage KFG on the 2.81 and it worked - Huh
It must be something to do with the KFG file but not being able to change it means I will probably have to start fresh.
I myself cannot run DX10 so rely on beta testers to report.
I must get a dual boot system but hate all the new O/S from the gates foundation - no disrepect - just to much crap trying to tell you what to do and auto tune.
 
IP Logged
 
Reply #5 - 31st Oct, 2010 at 1:48am

DaveNunez   Offline
YaBB Moderator
Seattle, Washington

Gender: male
Posts: 504
*****
 
Hmmmm.... iiinteresting...

(BTW, feel free to curse Windows, but if you say something bad about Exchange, prepare to duel outside!  Wink )

Any chance we can get a screenshot of the anomaly? Around the 2.6-2.7 timeframe I added a bunch of stuff related to bloom etc so it could be from that also.
 

Multimedia File Viewing and Clickable Links are available for Registered Members only!!  You need to Login or Register&&Multimedia File Viewing and Clickable Links are available for Registered Members only!!  You need to Login or Register
&&
IP Logged
 
Reply #6 - 31st Oct, 2010 at 4:36am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
no prob with exchange - I look after 2 servers running it.
I will see if I can sort out some screen shots
 
IP Logged
 
Reply #7 - 2nd Nov, 2010 at 4:35am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
OK Another thing I have found and again it could be unique to me - is when I add default MATERIAL properties and MATERIAL ALPHA properties in tweak it does not compile and gives error messages. Take them out or delete the settings and all is ok again.
 
IP Logged
 
Reply #8 - 2nd Nov, 2010 at 4:36am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
I am almost sure it is the way the KFG file is now parsed (or not  Huh)
 
IP Logged
 
Reply #9 - 2nd Nov, 2010 at 10:52am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Another thing while going through various trials. Aircraft compiled in FSDS and all textures had the "r" suffix removed from the texture properties and the aircraft as you would expect showed in the sim as rather flat and no shine. Starting from a clean KFG file and again compiling with tweak WITH NO TEXTURE ENHANCEMENTS added at all - just reference to the textures used - the aircraft compiled with a rather over-powering shine. I have not told tweak via the KFG to add any texture enhancements or special properties Shocked
 
IP Logged
 
Reply #10 - 2nd Nov, 2010 at 10:25pm

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Hi
Prob unrelated but do you or the user have bloom on in fsx under dx10?
try running the aircraft with it off
Wozza


 
IP Logged
 
Reply #11 - 3rd Nov, 2010 at 1:19am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Hi Wozza,
The person testing it for me has bloom turned off. The problem is that it is built with the same materials as the Mirage and the texture KFG peoperties are more or less identical but the Mirage did work in DX10 when it was compiled with a previous version a year or so ago.
 
IP Logged
 
Reply #12 - 3rd Nov, 2010 at 2:13am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Hi
I havnt done much testing in DX10 as I removed win7 and went back to xp
I found this cfg setup for my texan external model worked fine bar the bloom in dx10
not sure if its any help,I use the command line and enter the data in the cfg files by hand....maybe something in the following cfg dump will help (tweak ver 2.71c)


[texture.0]
identifier=Engine_T.bmp
specular=Engine_T_spec.dds
bump=Engine_T_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
NoShadow=1
AllowBloom=0

[texture.1]
identifier=glassx_t.bmp
diffuse=glassX_t.dds
specular=glassX_t_spec.dds
fresnel=Fresnel_Ramp_glass.dds
environment_level_scale=1
NoShadow=1
UseGlobalEnvironment=0
SourceBlend=SrcAlpha
DestinationBlend=InvSrcAlpha
AllowBloom=1
AmbientLightScale=1
EmissiveBloom=1
SpecularBloomFloor=0.9


[texture.2]
identifier=na_strut.bmp
specular=na_strut_spec.dds
bump=na_strut_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.3]
identifier=NA_TAILWHEEL.bmp
specular=NA_TAILWHEEL_spec.dds
bump=NA_TAILWHEEL_bump.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
AllowBloom=0

[texture.4]
identifier=NA16well.bmp
specular=NA16well_spec.dds
bump=NA16well_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.5]
identifier=prop.bmp
NoShadow=1
AllowBloom=0

[texture.6]
identifier=t6_tread.bmp
specular=t6_tread_spec.dds
bump=t6_tread_bump.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
AllowBloom=0

[texture.7]
identifier=TEXAN_t.bmp
specular=TEXAN_t_spec.dds
bump=TEXAN_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.8]
identifier=TEXAN1_t.bmp
specular=TEXAN1_t_spec.dds
bump=TEXAN1_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.9]
identifier=Texan2_t.bmp
specular=Texan2_t_spec.dds
bump=Texan2_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.10]
identifier=TEXAN3_t.bmp
specular=TEXAN3_t_spec.dds
bump=TEXAN3_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.11]
identifier=TEXAN4_t.bmp
specular=TEXAN4_t_spec.dds
bump=TEXAN4_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.12]
identifier=TEXAN5_t.bmp
specular=TEXAN5_t_spec.dds
bump=TEXAN5_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.13]
identifier=TEXANwingL_t.bmp
specular=TEXANwingL_t_spec.dds
bump=TEXANwingL_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.14]
identifier=TEXANwingR_t.bmp
specular=TEXANwingR_t_spec.dds
bump=TEXANwingR_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.15]
identifier=NA_tyreside.bmp
specular=NA_tyreside_spec.dds
bump=NA_tyreside_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.16]
identifier=Gauges.bmp
bump=Gauges_bump.dds
specular=Gauges_spec.dds
AllowBloom=0

[texture.17]
identifier=TEXAN6_t.bmp
specular=TEXAN6_t_spec.dds
bump=TEXAN6_t_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.18]
identifier=pilot.bmp
specular=pilot_spec.dds
bump=pilot_bump.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.19]
identifier=TEXAN7_t.bmp
specular=TEXAN7_t_spec.dds
bump=TEXAN7_t_bump.dds
environment_level_scale=1
bump_scale=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
AllowBloom=0

[texture.20]
identifier=Comp_Glass.bmp
diffuse=Comp_Glass.dds
AllowBloom=1
AmbientLightScale=1
EmissiveBloom=1
SpecularBloomFloor=0.9

[contact_global]
emergency_extension_type=0
gear_system_type=4
tailwheel_lock=0


footnote in this project there was only 1 material ......default to keep draw rate down ...yeh I know I kinda went overboard with the textures Smiley
Wozza


 
IP Logged
 
Reply #13 - 3rd Nov, 2010 at 2:33am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Interesting that you have all terms at 1 when required.
An extract of the KFG i have been using. Note that I think the spec power term can only be between 0 - 255 as this multiplys the specular alpha. So larger number smaller hot spot.
Now blend evironment by inverse of diffuse alpha is the reflection but - in the KFG or Tweak does "Environment_level_scale" = the reflection term in the SDK? If so then the numbers are all wrong. Or should it be the same range as the spec power term?

Strange thing is on the compile with errors the VC works fine but the external washes out with far to much reflection or specular. Both use the same textures and KFG values where required.

[texture.0]
identifier=chrome_T.bmp
reflection=GlobalEnv_AC_Chrome.dds
environment_level_scale=0.8
BlendEnvironmentByInverseDiffuseAlpha=1
SourceBlend=One
DestinationBlend=Zero

[texture.1]
identifier=DIALS_T.bmp
specular=DIALS_T_spec.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.5
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=300
SourceBlend=One
DestinationBlend=Zero

[texture.2]
identifier=DIALS2_T.bmp
specular=DIALS2_T_spec.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.5
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=500
SourceBlend=One
DestinationBlend=Zero

[texture.3]
identifier=Eng_T.bmp
specular=Eng_T_spec.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.3
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=300
SourceBlend=One
DestinationBlend=Zero
BloomModulatingByAlpha=1

[texture.4]
identifier=F1_T.bmp
specular=F1_T_spec.dds
bump=F1_T_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.3
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=300
SourceBlend=One
DestinationBlend=Zero
BloomModulatingByAlpha=1

[texture.5]
identifier=F2_T.bmp
specular=F2_T_spec.dds
bump=F2_T_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.3
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=300
SourceBlend=One
DestinationBlend=Zero
BloomModulatingByAlpha=1

[texture.6]
identifier=F2B_T.bmp
specular=F2B_T_spec.dds
bump=F2B_T_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.3
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=300
SourceBlend=One
DestinationBlend=Zero
BloomModulatingByAlpha=1

[texture.7]
identifier=gear_T.bmp
specular=gear_T_spec.dds
bump=gear_T_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.3
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=300
SourceBlend=One
DestinationBlend=Zero
BloomModulatingByAlpha=1

[texture.8]
identifier=gear2_T.bmp
specular=gear2_T_spec.dds
bump=gear2_T_bump.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=0.3
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelEnvironment=1
SpecularMapPowerScale=300
SourceBlend=One
DestinationBlend=Zero
BloomModulatingByAlpha=1

[texture.9]
identifier=GLASS_T.bmp
diffuse=GLASS_T.dds
specular=GLASS_T_spec.dds
fresnel=Fresnel_Ramp.dds
environment_level_scale=1
NoShadow=1
UseGlobalEnvironment=1
BlendEnvironmentByInverseDiffuseAlpha=1
FresnelSpecular=1
FresnelEnvironment=1
SpecularMapPowerScale=400
SourceBlend=SrcAlpha
DestinationBlend=InvSrcAlpha
 
IP Logged
 
Reply #14 - 3rd Nov, 2010 at 2:57am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Hi Mate
I have no idea on how it all works Cheesy for the most part I set the flags for default or low and then push it in the textures.....
Im not sure about
SourceBlend=One
DestinationBlend=Zero 
looking through the xfiles Ive never seen zero or one in verbose its always been numerical....but what do I know Smiley
also if the VC errors at tweak time the difference between ext and vc  might only be the textures showing in the orig compile mode ie fs9 style, Ive been caught out by that a few times.
Cheers
Wozza

 
IP Logged
 
Reply #15 - 3rd Nov, 2010 at 3:08am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Ps
quote
"Note that I think the spec power term can only be between 0 - 255 as this multiplys the specular alpha"

I leave that at the default for the material and use the 0 to 255 for the alpha channel in the spec map texture?
Im not sure where your at with fsx but materials are nothing nada diddle squat set them in fsds as default and forget them ..in FSX its all texture driven
Wozza
 
IP Logged
 
Reply #16 - 3rd Nov, 2010 at 3:08am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Source blend is the default for opaque = source blend one destination blend zero
All the textures are default FSX as is the project. Never been done in FS9 and I have not compiled a project for that for over 3 years.
The other thing I am trying to work out  - although not related to this is Z Buffer values.
I thing that it is also strange when I try to set "default" or fall back material properties that the compile throws up all sorts of errors regarding memory and animation. Take the settings out and it works fine - go figure  Huh
 
IP Logged
 
Reply #17 - 3rd Nov, 2010 at 3:12am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Au-MaV wrote on 3rd Nov, 2010 at 3:08am:
Ps
quote
"Note that I think the spec power term can only be between 0 - 255 as this multiplys the specular alpha"

I leave that at the default for the material and use the 0 to 255 for the alpha channel in the spec map texture?
Im not usre where your at with fsx but materials are nothing nada diddle squat set them in fsds as default and forget them ..in FSX its all texture driven
Wozza

Yes I understand the multiply on the spec power value.
I think you are wrong about materials in FSX. Even the SDK refers to base material properties and then goes onto texture properties.
It is the base material value that affects the reflective and the values given. I think that Tweak does not support this correctly but there is a section to implement this.
 
IP Logged
 
Reply #18 - 3rd Nov, 2010 at 3:14am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Quote:
Source blend is the default for opaque = source blend one destination blend zero
All the textures are default FSX as is the project. Never been done in FS9 and I have not compiled a project for that for over 3 years.
The other thing I am trying to work out - although not related to this is Z Buffer values.
I thing that it is also strange when I try to set "default" or fall back material properties that the compile throws up all sorts of errors regarding memory and animation. Take the settings out and it works fine - go figure Huh

Yep but fsds pumps out basic fs9 texture params by default in the xfile header, the reason we use tweak to fix that issue Smiley so if tweak fails you will have fs9 style texture params in your fsx mdl Smiley
 
IP Logged
 
Reply #19 - 3rd Nov, 2010 at 3:20am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Quote:
Au-MaV wrote on 3rd Nov, 2010 at 3:08am:
Ps
quote
"Note that I think the spec power term can only be between 0 - 255 as this multiplys the specular alpha"

I leave that at the default for the material and use the 0 to 255 for the alpha channel in the spec map texture?
Im not usre where your at with fsx but materials are nothing nada diddle squat set them in fsds as default and forget them ..in FSX its all texture driven
Wozza

Yes I understand the multiply on the spec power value.
I think you are wrong about materials in FSX. Even the SDK refers to base material properties and then goes onto texture properties.
It is the base material value that affects the reflective and the values given. I think that Tweak does not support this correctly but there is a section to implement this.

Not under fsds/fstweak its all texture driven, the materials settings in fsds are all ignored and pointless at compile time(as far as I can see)
If your not using g-max or 3d max then the sdk is basically useless in relation to modeling,scripts...material info
Wozza
 
IP Logged
 
Reply #20 - 3rd Nov, 2010 at 3:23am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Hi mate,
Yes I know but if the same texture works in the VC environment with the same texture properties then why not on the external?
The cockpit frame is an example.
Base Colour section in tweak should enable or convert the x file to adjust the base material properties.
Still all this is proving interesting  Grin
The thing that is bugging me is that it is probably something I have done but it is strange when you have been using a recipe for a few years and then it no longer works when you change the oven.
 
IP Logged
 
Reply #21 - 3rd Nov, 2010 at 3:37am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Quote:
Hi mate,
Yes I know but if the same texture works in the VC environment with the same texture properties then why not on the external?
The cockpit frame is an example.
Base Colour section in tweak should enable or convert the x file to adjust the base material properties.
Still all this is proving interesting Grin
The thing that is bugging me is that it is probably something I have done but it is strange when you have been using a recipe for a few years and then it no longer works when you change the oven.

Hi Mate
The only things it can be if both params are the same for the ext vc, is fstweak is bombing out and not processing the texture info in one of the models,the video card drivers or dx10 install on the test system are pooched.when this sort of thing happens goto to KISS just build a box for the ext and vc , use one texture set and cfg params and test
if that works fine then you at least know the issues in the main project somewhere and not the tools Cheesy
Wozza
 
IP Logged
 
Reply #22 - 3rd Nov, 2010 at 3:43am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Hi
The thought had crossed my mind  Wink but -
It was working fine in DX10 as earlier beta's proved.
Now I have a hunch that when update 2.81 was implemented because of the $pan1, $pan2 issue it may have changed other stuff in the way the KFG is parsed.
I will try it out by going back to 2.8 if what I am doing at the moment still does not work.
 
IP Logged
 
Reply #23 - 3rd Nov, 2010 at 4:49am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
OK, Update.
The model has now been tried again in DX10 with only one texture enhancement in the KFG and shows correctly with and without bloom.
Re building the KFG to see what happens.
 
IP Logged
 
Reply #24 - 9th Nov, 2010 at 2:04am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Au-MaV wrote on 3rd Nov, 2010 at 3:08am:
Ps
quote
Im not sure where your at with fsx but materials are nothing nada diddle squat set them in fsds as default and forget them ..in FSX its all texture driven
Wozza

I have re-written the KFG's for the model and it now works in DX10 mode.
Regarding the materials in FSDS and tweak.
I have found that if you leave the base material as "default" but have spec maps and these are referenced in the KFG for the textures - when you compile with Tweak - no mention of the enhanced material is made so possibly the enhancements are skipped. You may even get a warning in the "bat" window that "removing specular from material as no base specular has been set" or words to that effect.
Now if you set a specular value in the base material property in FSDS that warning disappears.
It all depends on how you configure your textures for the model etc BUT it does have a visual effect in the sim AND is processed on compile.

I will post more when I have found out what the effects are.
 
IP Logged
 
Reply #25 - 9th Nov, 2010 at 2:44am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Quote:
Au-MaV wrote on 3rd Nov, 2010 at 3:08am:
Ps
quote
Im not sure where your at with fsx but materials are nothing nada diddle squat set them in fsds as default and forget them ..in FSX its all texture driven
Wozza

I have re-written the KFG's for the model and it now works in DX10 mode.
Regarding the materials in FSDS and tweak.
I have found that if you leave the base material as "default" but have spec maps and these are referenced in the KFG for the textures - when you compile with Tweak - no mention of the enhanced material is made so possibly the enhancements are skipped. You may even get a warning in the "bat" window that "removing specular from material as no base specular has been set" or words to that effect.
Now if you set a specular value in the base material property in FSDS that warning disappears.
It all depends on how you configure your textures for the model etc BUT it does have a visual effect in the sim AND is processed on compile.

I will post more when I have found out what the effects are.

Hi
Im doing this from a gray foggie memory its been a while since I did anything in fsds:)...... But if you specify a spec map you also need a fresnel= pram or you get the error
"no base specular has been set"....I think...... I know Ive seen the error before and it was a missing pram in the KFG file
as I said I did the freeware texan with only a default material,it all came out as I had wanted/expected but. Im no expert so its possible something was missing or not working in the final model.
Wozza
 
IP Logged
 
Reply #26 - 9th Nov, 2010 at 2:59am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
The last model I released was the Skysim Mirage for FSX using Tweak.
The Fresnel is referenced to affect reflective in the KFG for the new project.
Something has changed with the upgrades of tweak and when compiling my old Mirage models with the Old KFG's they appear completely different in the sim.
I think that it may be hinted on this thread:
Multimedia File Viewing and Clickable Links are available for Registered Members only!!  You need to Login or Register
I think that this occurs in FSDS 3.51 but the tweak ignores it rather than gives errors.
I can only go on what the final model looks like in the sim.
Maybe try and re-compile your old model again with the new version of tweak and see if you spot any changes in appearance in the sim using the old KFG files.
 
IP Logged
 
Reply #27 - 9th Nov, 2010 at 6:42am

Au-MaV   Offline
Inspecteur des Polygonnes
Whatcha lookin at
Adelaide South Australia

Gender: male
Posts: 1956
*****
 
Hi Mate
Yep already did that as I didnt realize I was using an older ver of fstweak came out fine...but then I do fsxtweak manually via dos and cfg's
As I said its been awhile sinse I did any work in fsds so I may of got it arse about Wink

Wozza
 
IP Logged
 
Reply #28 - 9th Nov, 2010 at 9:10pm

DaveNunez   Offline
YaBB Moderator
Seattle, Washington

Gender: male
Posts: 504
*****
 
Hi guys

I must admit, I am pretty confused... do we have a clear bug in 3.5.1 and tweak 2.8?

The issue with 3.5.2 is totally separate though - that is due to the fact that the tweaker will not put up materials most of the time when the .x file is generated by 3.5.2.

If someone can send me a .X file which used to work, and now does not, I can run it through older versions of tweak until we see the change.

Paul, perhaps you can send me a .x file of your mirage, plus the kfg file?
 

Multimedia File Viewing and Clickable Links are available for Registered Members only!!  You need to Login or Register&&Multimedia File Viewing and Clickable Links are available for Registered Members only!!  You need to Login or Register
&&
IP Logged
 
Reply #29 - 10th Nov, 2010 at 2:31am

FSDSMAN   Offline
LDV Engineer
This was ment to be fun
The Garden Of England

Gender: male
Posts: 354
****
 
Hi Dave,
I will email you the KFG's for the Mirage and the current project. I am close to finishing the current project and do not want to revert back to an old compile but I will be re-compiling the Mirage with a few enhancements so I will sort out the X files from that.
Basically If in FSDS I add a specular colour and power into the material properties used then when I run Tweak I get no errors and visually in the SIM the aircraft looks better than if I left the material as "default"
What is confusing is that in FSX the material is meant to be ignored before tweak?
If you set a specular value in FSDS and a specular power on the material then Tweak does read it from the X file. Strange as this is not meant to happen?
pm me with your current email
Regards
Mark
 
IP Logged
 
Pages: 1 
Send Topic Print