AGlobeAwareDefaultPawn modification. Nodes not accessible in blueprint

ed_99 · August 7, 2023, 5:04pm

Hello I’m trying to modify the AGlobeAwareDefaultPawn so I can move the camera in a different axis.
I added these lines to the header file:

UFUNCTION(BlueprintCallable, Category = “Movement”)
void MoveUp_View(float Val);

and these line to the cpp file
void AGlobeAwareDefaultPawn::MoveUp_View(float Val) {
this->_moveAlongViewAxis(EAxis::Z, Val);
}

which is basically the same than MoveRight method, but using different axis.

Could you help me to find out why I can’t access to the MoveUp_View in my level blueprint. and why in the level blueprint I can only access the moveRight function of the DefaultPawn and not the one belonging to AGlobeAwareDefaultPawn as I’d like to?

Thanks in advance

Kevin_Ring · August 7, 2023, 10:18pm

You can’t access MoveRight in AGlobeAwareDefaultPawn from Blueprints because it’s not marked as a UFUNCTION. Your new MoveUp_View is, though, so I would expect that to work. But you’ll need to recompile the plugin after you’ve changed the C++ code. Have you done that?

ed_99 · August 8, 2023, 5:47am

Hello, thanks a lot for your reply. I thought i did that, as I recompiled the project in visual studio after making the changes.
is that what you mean when you say recompiling the plugin? or am I missing a step I should take to recompile the cesium related content?
I also marked MoveRight as UFUNCTION in the AGlobeAwareDefaultPawn class, but I can only access the MoveRight from DefaultPawn in ue5, not the one from AGlobeAwareDefaultPawn.

Thanks again for your answer. Much appreciated

Kevin_Ring · August 8, 2023, 6:06am

Is the plugin in your project? If it is, compiling the project in Visual Studio should also build the plugin. But if the plugin is in the Engine/Plugins directory (as it would be if you installed it from the UE Marketplace), compiling your project won’t do anything to compile the plugin.

ed_99 · August 8, 2023, 6:20am

Hello Kevin. thanks again for your reply. I’m afraid yes, my cesium plugin is in my Engine/Plugins directory. Based on your comment, is there a way to change that?, so the cesium plugin gets recompiled when compiling the visual studio project.

One million thanks

Kevin_Ring · August 8, 2023, 6:36am

You can follow the Developer Setup instructions:

github.com

CesiumGS/cesium-unreal/blob/ue5-main/Documentation/developer-setup.md

## Overview

This is a summary of a setup and workflows for developers who want to work with the *Cesium for Unreal* plugin. Such a setup consists of three main components:

- [`cesium-native`](https://github.com/CesiumGS/cesium-native) : A collection of engine-independent libraries for 3D Tiles, geospatial, etc. Most of the functionality of *Cesium for Unreal* is built based on these libraries.
- [`cesium-unreal`](https://github.com/CesiumGS/cesium-unreal) : The source code of the actual *Cesium for Unreal* plugin.
- An Unreal project that uses the plugin. We will use the [`cesium-unreal-samples`](https://github.com/CesiumGS/cesium-unreal-samples) as an example here, to get started quickly. It contains sample levels for different use cases, and can therefore be used to quickly check for possible regressions of feature changes.

> Note: It is generally possible to work with `cesium-native` *independent* of `cesium-unreal`. But any modification in `cesium-native` will have to be checked carefully for possible breaking changes in the API or the build process. So the following describes the developer setup from the perspective of someone who wants to work with `cesium-native` mainly in the context of `cesium-unreal`.

## Principles

There are detailed instructions for setting up a Cesium for Unreal development environment on each platform. But if you're already used to doing this sort of thing, you can probably use whatever workflow you like as long as you follow some important principles:

- To build Cesium for Unreal, you must first compile and cmake-install cesium-native and its dependencies to `Plugins/cesium-unreal/Source/ThirdParty`.
- cesium-native is built and installed using CMake and the `CMakeLists.txt` found in the `cesium-unreal/extern` directory, _not_ the one in the `cesium-unreal/extern/cesium-native` directory. When installing from this directory, the default install path will put cesium-native where Cesium for Unreal expects to find it.
- You must use the same compiler to build cesium-native and Cesium for Unreal.
- On Windows, packaging the Cesium for Unreal plugin on Windows requires Visual Studio 2017. This means you must also build cesium-native with Visual Studio 2017 in order for plugin packaging to be successful. But if you're not concerned with packaging, you can use Visual Studio 2019 exclusively.
- The Unreal project "DebugGame" configuration tries to use the debug build of cesium-native if one is built and installed, and falls back on the release build otherwise. The "Development" and "Shipping" configurations use the release build exclusively.
- Our CI build process checks for formatting using clang, and fails if code is improperly formatted. To run clang on all source code before committing, run `npm ci` to install node modules, then `npm run format`.

This file has been truncated. show original

You may be able to skip some steps and simply copy the installed plugin into [your project]\Plugins\CesiumForUnreal, rather than building it from source from scratch. I haven’t tried that in a long time, but I think it will work.

ed_99 · August 8, 2023, 6:51am

Thank you soooooo much!!. I will definitely try that. Thanks a lot for your help. it’s so much appreciated. Have a great day!!!

ed_99 · August 8, 2023, 2:19pm

hello! just to say thanks. that solved the issue! Thank you so much!
For the record, I took the easy approach (moving the folder, generating the vs files, compiling in VS and it worked!
Thank you!!!