Performance rendering of dSPACE

DSPACE Performance rendering problems for

Problem description

In the use of DSPACE The platform builds a complex scenario , stay ModelDesk Normal road construction and script writing can be carried out in . however , Download to MotionDesk When preparing to simulate the scene , Find out ModelDesk Keep popping up and reporting errors , Can't download to MotionDesk in .

ModelDesk The details of error reporting are as follows ：

To solve the process

One 、 Check the scene

We first checked whether the road was built incorrectly , For example, the corner between roads is too large, and the setting is too large, resulting in non-compliance DSPACE Basic setting of 、 The specified road has no and Junction Connection and so on .

I checked it carefully , I found that there was no problem in road construction , All the points that should be noted are green indicating passing . Try downloading again , This error is still reported .

Two 、 Restart and replace

We consider whether it may happen occasionally during the software operation bug, So it will DSPACE The series software is restarted . Try downloading again , The error has not disappeared .

Since it's not runtime bug, We consider whether the project is too big , There are too many things , And cause hidden errors .

Then we rebuilt a new project , Try downloading this scenario again under the new project , The error is still reported .

3、 ... and 、 The wrong location

Common methods can not quickly solve the problem of error reporting , Therefore, we still have to locate the error report , After a series of surveys , Finally in the MotionDesk Key error messages are found in .

Each download will generate four error messages , The first three of them surround Road 1 Always emphasize mistakes , But there is no explicit reason for the error . Only article 4 details what has happened , Let's turn it on .

The meaning of this passage is to say ： No road network is generated , Please make sure that in this directory CIDAS_2203160047.rd The file has the appropriate dimensions for the corridor elements used to generate the geometry .

among , It is a conclusion that the road network is not generated , The reason for this conclusion may be rd The road elements in the file are improperly sized .

---

Good! , To this step , The feeling is already obvious , There should be a problem with one of the lanes in the road .

So I built the scene again with the image , Ensure that each lane and each intersection comply with the regulations .

However, it doesn't make any difference , This error is still reported when downloading , It makes people convinced .

Four 、 Troubleshooting

I really don't understand why I keep reporting errors , We wonder if there is something wrong with the software , But after changing the scene , No matter downloading or emulating, there is no problem . No way out , We can only turn to the technical personnel of the company .

After copying the scene to the technician , The technician said there was no problem running on his computer , Very smooth .

This result makes us have to suspect that it is a computer problem , So we copied the scene to another computer with the same configuration . As a result, it is still unable to run on this computer with the same configuration , The same mistake .

Then copy it to a computer with better performance , And there was no mistake .

Conclusion

Through such a set of troubleshooting process , We come to the conclusion that ：

For some complex scenes , stay MotionDesk The requirements for computer performance are relatively high when rendering in .

But particularly complex scenes are rare , For ordinary scenes , Ordinary game books can still run .