# PointLoad - Eccentricity

**URL:** <https://femdesign.discourse.group/t/pointload-eccentricity/620>\
**Category:** Grasshopper\
**Tags:** waiting\
**Created:** [2 October 2026 15:45 UTC](https://femdesign.discourse.group/t/pointload-eccentricity/620 "2026-10-02T15:45:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndreiM](https://dub1.discourse-cdn.com/flex017/user_avatar/femdesign.discourse.group/andreim/32/393_2.png) [@AndreiM](https://femdesign.discourse.group/u/AndreiM)\
**Post date:** [2 October 2026 15:45 UTC](https://femdesign.discourse.group/t/pointload-eccentricity/620/1 "2026-10-02T15:45:02Z")

</div>

Hey

I’m trying to access the eccentritcity feature for loads in FEM-Design through Grasshopper, but so far I haven’t been able to find a way to do it.

Is this function currently exposed in the FEM-Design API? If not, does anyone know of a workaround, through a C#/Python script component or another method?

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/2X/0/0984838c4068e7534fa985975af3e5b133e8c88a.png)

---

<div class="post-metadata">

**Author:** ![anLor](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@anLor](https://femdesign.discourse.group/u/anLor)\
**Post date:** [13 October 2026 13:10 UTC](https://femdesign.discourse.group/t/pointload-eccentricity/620/2 "2026-10-13T13:10:31Z")

</div>

Hey @AndreiM! 👋

Unfortunately, this feature is not implemented in the Grasshopper package or our SDKs. I have opened a ticket that you can track via this link: [Load excentricity properties of PointLoad/LineLoad/SurfaceLoad are missing #1213](https://github.com/ms-structural/femdesign-api/issues/1213)

As a workaround, have you tried using the `Fictitious bar` functionality? This is a classic modelling solution for taking load eccentricity into account by modelling it physically. Of course, you need to use a very rigid bar, and if the eccentricity is very large, this will be reflected in the results. I’ve attached a FEM-Design example file below.

[load\_ecc-with-fict-bars.zip](https://femdesign.discourse.group/uploads/short-url/svTljMIkAt2KJVFNQOJN2PgGIkB.zip) (191.4 KB)

![fict-bar-example](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/2X/8/8fb5cc3d2af760f194affdda79bc25d4e0c7966b.gif)

The `Fictitious bar` is available in Grasshopper, so this can be reproduced via the API.

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/2X/5/5250763b142e5a2f0d097af28cefc2b788fad8e0.png)

---

<div class="post-metadata">

**Author:** ![AndreiM](https://dub1.discourse-cdn.com/flex017/user_avatar/femdesign.discourse.group/andreim/32/393_2.png) [@AndreiM](https://femdesign.discourse.group/u/AndreiM)\
**Post date:** [14 October 2026 06:49 UTC](https://femdesign.discourse.group/t/pointload-eccentricity/620/3 "2026-10-14T06:49:58Z")

</div>

Hey @anLor 😃

Thank you for the example. It works well when dealing with one or a few elements.

In my case, however, I have several shells with various line loads and point loads, each with different eccentricities, so I’d like to avoid creating too many fictitious bars.

I’m glad to hear this will be implemented, as I think it will be very useful.

As a workaround, I currently use a C# component that saves the initial model as a struxml file and then modifies the eccentricity for specific load cases or loads, based on their GUID and the desired eccentricity and saves it as a new struxml.
