• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Mouse Rect Attach Point?(Solved)

Hm, any vc panel texture with a dollar-sign prefix ($) should NOT have a real texture at all. The $ prefix is a flag to tell FS to dynamically create a memory texture on which to project the gauges.

However, your problem appears to be in the actual model's source file itself. Since you are using Blender, I have nothing useful to suggest since I use only Max (and occasionally GMax for some really old stuff)...

EDIT: You might try 'un-linking' the gauge projection polygons from their parents, and compile again. I've never heard of a parent object 'inheriting' from the children objects, but one never knows...
 
Last edited:
Hi Mr. Bill Leaming!

For the applying a texture to the poly used for the vc panel. I thought that you had to apply a texture to the poly used as a panel so that FSX knows that it is a vc panel. I use the tutorial that you made named "VC Gauge Backlighting - A Tutorial Using Emissive Texture Lightmapping ".

I use this tutorial that you made every time that I made a VC panel in GMax.
I have not had this issue in Gmax; But that does not mean that I did not do something wrong.

Thank you very much for looking at my model. I will try what you suggested, and I will let you know what happens.

Thank you very much, Mr. Bill:D

Krispy1001:)
 
Hm, any vc panel texture with a dollar-sign prefix ($) should NOT have a real texture at all. The $ prefix is a flag to tell FS to dynamically create a memory texture on which to project the gauges.

However, your problem appears to be in the actual model's source file itself. Since you are using Blender, I have nothing useful to suggest since I use only Max (and occasionally GMax for some really old stuff)...

EDIT: You might try 'un-linking' the gauge projection polygons from their parents, and compile again. I've never heard of a parent object 'inheriting' from the children objects, but one never knows...

OK, color me stupid!:banghead: All the time that I used your tutorial to make my VC's in Gmax I always applied a real texture to my panel poly in FSX. I just now understand that I do not have to do that. (And you do not say too do that in your tutorial.) I guess I just decided that myself. I will have to let everyone know that the Blender2FSX video that I did on the panels. You do not need to make a .dds file.:banghead:

Ok, now for the un-parenting my panel poly's. It did not make a difference. So I am back to square one.

Thank you Mr. Bill for setting me straight on not applying a real texture to panel poly's for FSX!!!!:D

Krispy1001:)
 
For the sake of efficient troubleshooting (and to avoid possible confusion) let's just focus on one part. You pick it. To start off what I am interested in is this...

1. What the part is supposed to do.
2. Is the part 3d modeled or a 2d gauge?
3. How is the MouseRect currently assigned to the part?
 
Hi all,

I got Kris' model and experienced the following (the same as Kris experiences);

- At first startup (clean as I downloaded the thing), everything is fine. I can click all spots, only the GPS is not displayed because it is commented out.
- Then I enable the GPS via the panel config file.
- Now it displays GPS, but the entire fuselage is mouse rect (hand cursor with a minus sign, most probably a GPS thing). If you move outside the fuselage, the world is no mouse rect.
- Disabling the GPS disables all mouse rects, it seems.
 
For the sake of efficient troubleshooting (and to avoid possible confusion) let's just focus on one part. You pick it. To start off what I am interested in is this...

1. What the part is supposed to do.
2. Is the part 3d modeled or a 2d gauge?
3. How is the MouseRect currently assigned to the part?

Hi Mr. N2056!
I am using 7 polys that I have applied a vc panel texture to. I will be using these to apply an instrument to in my main panel. I have so far 4 3d animated objects that have a mouse rect applied to in on my main panel. (“The 3d objects are: main power switch, avionics power switch, throttle, mixture”)

When I test my model in FSX with all of the Vcockpit views active in the panel.cfg file, my mouse rects do not work. And the last Vcockpit view “GPS” uses the whole fuselage as it's panel. Now if I move the mouse pointer on the the individual instrument, the mouse rect for that 2d instrument works fine. But none of the mouse rects work for the 3d objects used for power, avionics, throttle, and mixture. And I believe this is happening because the GPS instrument sees the whole fuselage as it's panel.

Steps I have taken so for to fix this problem:

1. I have re-modeled most of my VC cockpit model, so that I could pay close attention to what I was doing and making sure that I did not make any polys that may be blocking the polys that will be used for instruments and my 3D objects with mouse rects applied.
2. I deleted all of my original textures used for my vc panel textures. And I re-made them.
3. I have started a new blender file and re-modeled my instrument panel and all polys. I did this to test and see if I had a corrupt file. I then tested in FSX just my instrument panel and instruments. The test gave the same results.
4. I made my Jodel FSX file available for other people to test and see if they have the same problem as I do. Mr. Daan (DutcheeseBlend) has verified that he has the same problem with his system with my model. So that eliminates my system as the problem.
5. I un-parented the polys used for my instruments from the main body as Mr. Bill Leaming(n4gix) suggested. That did not help.
6. I have talked to Mr. Felix(Capt_X) too se if he can see anything that I may have done wrong. And to see if maybe it is something that the Blender2FSX addon may be having a problem with.

I do not know what else to try! It kinda takes the wind out of your sails when something so simple gives you so many problems.
I thank everyone that has helped me so much in the past. And I appreciate all the help you guys are giving me now.

Thank you very much Mr. N2056!!!!!!!

Thank you, Kris:)
 
Tried assigning a different $panel material to the GPS?

Hi Mr. Heretic!

Yes I have made all new textures used for vc panel textures. I made the files as followed: 256 x 256, 8bit indexed saved as a .bmp file.

I had the same results.

Thank you very much Mr. Heretic for you Help!:D

Krispy1001:)
 
Hi all,

I got Kris' model and experienced the following (the same as Kris experiences);

- At first startup (clean as I downloaded the thing), everything is fine. I can click all spots, only the GPS is not displayed because it is commented out.
- Then I enable the GPS via the panel config file.
- Now it displays GPS, but the entire fuselage is mouse rect (hand cursor with a minus sign, most probably a GPS thing). If you move outside the fuselage, the world is no mouse rect.
- Disabling the GPS disables all mouse rects, it seems.

Thank you Mr. Daan(Dutcheeseblend) for all your help!!!!!!:D

Krispy1001:)
 
For the applying a texture to the poly used for the vc panel. I thought that you had to apply a texture to the poly used as a panel so that FSX knows that it is a vc panel. I use the tutorial that you made named "VC Gauge Backlighting - A Tutorial Using Emissive Texture Lightmapping ".
You only need a file named $VC1 (or some other name) in the modeling program. Only the $name is actually used.

Also, you really should not use so many gauge polygons. Just one would be enough, or at most two! One for the few 'round' gauges, and one for the GPS.
 
Hi Mr. Bill Leaming!

Thank you very much for your help! And thank you for writing the tutorial "VC Gauge Backlighting - A Tutorial Using Emissive Texture Lightmapping ". It has helped me a lot.

I have solved my problem. (I have a corrupt object in my VC model.)

I have not been able to find which one is responsible yet. But now I at least know it is not Blender or Blender2FSX add that is causing the problem.

How I discovered this, is I added a 3d object as a throttle in my test plane that I used for the Blender2FSX videos. And it and my 2D gauges work perfect.

So, I will have to completely re-model my VC.

Thank you, Thank you, Thank you for everyone's Help!:D

sincerely, Kris:)
 
Hi everyone!

Well my mouse rects working randomly when using 2D gauges has been solved, by my Very Good Friend Mr. Felix aka(Capt_X).

Here is what he discovered:

("Hello Kris!

I have been fiddling around with your Jodel VC again today and I found out something strange: Mouserects will work if the materials of the object have a diffuse texture assigned.

I know that you are in the habit of using bare materials instead of textures but here is an important point about that: Every single material is a drawcall. The more drawcalls, the heavier your model gets on the CPU and the lower your FPS. Minimizing drawcalls is even more important than minimizing polygon count, so we always try to keep material count as low as possible. Hence, the use of textures. I noticed that except for gauge textures, none of your materials had textures applied to them...

Here is what I did:
  1. I started a new .blend file and deleted the default cube, camera and lamp.
  2. I appended (Shift+F1) the following parts of your existing VC to the scene: body_Inside, atitudeInstrument, throtelHandel and mixtureHandel.
  3. I then added some lighting to the scene and baked a full render of the materials on throtelHandel to a texture that I called lever_throttle.png.
  4. Then erased both materials of throtelHandel and replaced them by a new one called lever_throttle,
  5. went to the textures tab, and added lever_throttle.png to the first texture slot of the newly created material.
  6. Exported the model.
Now the throttle mouserect worked perfectly but the mixture mouserect wouldn't show... The throttle had a texture applied whilst the mixture hadn't. Do you get where I'm going? I think, for some silly reason, that if you apply textures to the mouserect parts, they should work. However, the strangest things have kept happening with your VC since I got it: sometimes mouserects were working, sometimes not. It all seemed very random. Maybe this time, we've pin-pointed the cause of all troubles, I don't know. Just thought it was worth giving you a shout...")

So I made this problem my self by being lazy and not making textures to test my model in FSX. I have a bad habit that I must break now. I can not use simple materials to test my models in FSX.:oops:

****** Everyone that has watched my Blender2FSX tutorials "I AM VERY SORRY THAT I HAVE TAUGHT YOU WRONG."*******

I will make a new video tutorial amending my errors. I Am Very Sorry!!!!!!!!!!!!!!:banghead::banghead::banghead:

Do not apply only simple materials to test your models in FSX. You will have problems like I have. My next videos will apply textures correctly to a model. So this will not happen again.

Thank you Mr. Felix(Capt_X) Thank you, Thank you, Thank you!!!!!:D:D:D:)
 
Back
Top